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

• Related Articles

• XAC: OBEY doesn't work from a XYGATEAC (XAC) TACL

  Reconcile COMMANDESCAPE character defined in the ACCONF file with those used in conjunction with the ALIAS keyword in the individual commands in the ACACL file 1. Edit the ACCONF file 2. Look for the line "COMMANDESCAPE". This should be near the top ...

• HPE: Receiving "Invalid User Name or Password" Error Message When Attempting to Logon at a TACL

  1. Check into whether the password contains any TACL metacharacters. The following are defined by HPE as TACL metacharacters: Character(s) Name Description [] Square brackets Causes TACL to expand the enclosed text == Double equal signs Specifies a ...

• 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 ...

• XAC: Error 48 when executing an obey file in an XAC TACL session

  Add the following keyword to the underlying TACL session (the XAC TACL session configured in the telnet service): 1. Edit the ACACL file 2. Add the keyword to the TACL command that is configured in the telnet service, e.g TACL-DYNAMIC-IP: ...

• XAC: How to configure XAC TACLs for static SSH windows

  Add a static service via the SSH STNCOM utility Example: STNCOM $<process name> (Where $<process name> is the name of a valid STN process, e.g. $ZPTY ADD SERVICE AUDTACL, TYPE STATIC 2. The service added in step #1 will need several static windows ...