Problem: The run condition word contains 075 in T3 following UACS execution and normal termination. Solution: UniAccess 10R1-3, 10R2-1, 10R3-0, and up have been modified to not change the run condition word. The run condition word at program termination will contain the same value of the run condition word at UACS initiation.

Read More

Knowledge Base: Running UACS

Problem: The CSPROC free chain introduced in 9R2 is getting corrupted such that freed PIDs become orphans until UACS declines new connections because the Free Chain indicates no CSPROCs are available, when in reality they are. Solution: This is resolved in UniAccess 10R1-2, 10R2-0, 10R3-0 , and up.

Read More

Knowledge Base: Running UACS

Problem: In a TIP session control environment and/or if a LOGOFF transaction is used, the UACS trace file can receive many [85], [48], and [38] errors. Solution: This is resolved in UniAccess 10R1-2, 10R2-0, 10R3-0 and up.

Read More

Knowledge Base: Running UACS

Problem: UACS can hang and the CSPROC D-bank corrupted when an MCB output message has a total length greater than 512 characters. Solution: This is resolved in UniAccess 10R1-0, 10R2-0, 10R3-0 and up.

Read More

Knowledge Base: Running UACS

Problem: Occasionally UACS receives QItems for CSPROCs which are not in use or are not linked to the originating MMPROC. This may lead to bad CSPROCs. Solution: This is resolved in UniAccess 10R1-1, 10R2-0, 10R3-0 and up.

Read More

Knowledge Base: Running UACS

Problem: When UACS encounters a trace file cycle conflict it leaves the test-and-set lock on the UniAccess Trace File and eventually this causes all UACS activities to queue. Solution: This is resolved in UniAccess 10R1-1, 10R2-0, 10R3-0 and up.

Read More

Knowledge Base: Running UACS

Problem: ST UACS results in: Invalid product key. [94] *ERROR* Solution: UniAccess levels 9R1 and above require a new product key. Update the OSPARM product key parameter(s) in the UniAccess Configuration File with the new product key(s) and deactivate and reactivate the UniAccess Fixed-gate.

Read More

Knowledge Base: Running UACS

Problem: ST UACS results in: No product service permissions exist in product key [92] ERROR Solution: Verify that the correct value was entered for the product key parameter(s) of the OSPARM statement. Deactivate and reactivate the UniAccess Fixed-gate. If this does not resolve the problem, please contact UniAccess Support: Email or phone UniAccess support. Note […]

Read More

Knowledge Base: Running UACS

Problem: When UACS is executed, a Basic Mode CMS Call Error [CMINIT] with a status of 4000000000001 is received. Solution: Verify that MCB is active in the appropriate application group.

Read More

Knowledge Base: Running UACS