XPQ: PQCONF syntax error Invalid ALGO

• Related Articles

• XPQ: XPQ license without \ENCRYPT causes 'Invalid ALGO' error

  To resolve XPQ syntax errors in the PQCONF file with 'Invalid ALGO', the XPQ license file needs to be updated with the new one containing the \ENCREPT entry. < example of XPQ license file containing the \ENCRYPT entry > PRODUCT: XYGATE-PQ 20291231 ...

• XPQ: XPQ_SYNTAX_CHECK returns 'Product 15 - file open <xpq-installation>.p15f001 failed - 32'

  The XYGATEPQ program object file has a PROGID feature, but when performing a syntax check, XYGATEPQ reads the license file p15f001 and XPQ configuration files using the CAID. When XYGATEPQ fails to read XPQ license file (p15f001), the ...

• XPQ: XYGATEPQ now supports AES256 encryption for changing passwords across all NonStop nodes

  As of version 3.50 XPQ uses 256-bit AES encryption method if all nodes in your XYGATEPQ environment are upgraded to version 3.50 or later and the ENCRYPTION keyword in the PQCONF of all nodes include a value of AES,<key> pair, e.g. ENCRYPTION ...

• XPQ: dh1024 encryption is ignored for XPQ version 3.20 and greater.

  Q. The softdoc for 3.20 says it will "ignore" "dh1024" part of "des168,dh1024". Encryption is still done using the algo in the first argument. What was changed was the key generation method, the key is generated internally now, so the "dh1024" is ...

• XAC: Eight character volume name causes Invalid OBEY file error.

  Verification: TACL> VOLUME TACL> OBEY $LONGVOL.A234567.XX XAC - Invalid OBEY file. Workaround: After using the XAC VOLUME command use the TACL SYSTEM command without an argument to set the system name to a blank value. TACL> SYSTEM TACL> OBEY ...