Problem: A new COMSRV parameter has been added that allows a site to switch the UACS unique-ID feature on (YES) or off (NO). The default is YES. The format for the new parameter is: COMSRV [AUXUNIQID, {YES | NO}; ] This UACS unique-ID is a 3 word field and is consistent during the UACS execution. […]
Read MoreKnowledge Base: Configuration Issues
Problem: The following error was encountered after increasing PIDCNT: [18] *ERROR” – TIP$SM call [Open Request] failed [7]. Solution: UniAccess 10R1-3, 10R2-1, 10R3-0, and up have been modified to correctly calculate the number of access control words (ACWs) that are required on the RT$PID request to reserve the PIDs.
Read MoreKnowledge Base: Configuration Issues
Problem: After UACS has been executed, it returns the following message: “UACS*PID ASSIGN/RELEASE ERROR [42] [12]”. Solution: UACS Console Message #12 (documented in the UniAccess for OS 2200 System Administration Guide) directs the reader to the Unisys Transaction Processing (TIP) Administration & Operations Reference for information on error 42. Section 25 of that manual describes […]
Read MoreKnowledge Base: Configuration Issues
Problem: After UACS has been executed, UARS (or any RPC) returns the following message: “[14] Basic Mode CMS call error [cmstor] [400000001006].” Solution: Verify that the OSPARM SESSCTRL parameter is valid in the UniAccess Configuration File. YES indicates that TIP session control is configured. NOindicates that TIP session control is not configured. Defaults to NO.
Read MoreKnowledge Base: Configuration Issues
Problem: The trace file displays the following message: “TIP$SM call [%s] failed [%o] affecting User = [%s], pid = [%d].” Solution: This error message is documented in the Unisys Transaction Processing (TIP) Administration & Operations Reference. The message may indicate invalid APPINF APPNAME or OSPARM SESSCTRL settings. Verify that these settings are correct in the […]
Read MoreKnowledge Base: Configuration Issues
Problem: After updating the UniAccess Configuration File, UARS (or any RPC) returns: UniAccess error #33800: “UACS error: Transaction UARS schedule failed (cmstor failed 400000000034).” Solution: Verify that the UniAccess Configuration File includes valid PIDs within the correct MCB. Note that these PID numbers cannot be in use by MAPPER or CMS.
Read MoreKnowledge Base: Configuration Issues
Problem: After the Configuration File has been updated, the change does not take effect. Solution: Make sure you have processed the UniAccess Configuration File with the proper options. Refer to the UniAccess for OS 2200 System Administration Guide for the correct procedures to initially execute and reconfigure the UACF processor. To verify that the changes […]
Read MoreKnowledge Base: Configuration Issues
Problem: UniAccess 9R2 and Greater Product Key Compatibility Issues With ClearPath Systems Running EXEC 46R4, 46R5, or 46R6. Solution: Review this document to see if your site needs to apply this TCF.
Read MoreKnowledge Base: Configuration Issues
Problem: After installing UniAccess 10R2-0, UACF returns the following message: “Invalid product key [UACLPRODKEY]. [26] *ERROR* UACF processing failed” even though the product keys are correct. Solution: Review this document, UniAccess updates are required with the EXEC in CP IX 9.2 (47R4B), CP IX 10.1 (47R5B), or later due to ER-CONFIG$ changes. to see if […]
Read MoreKnowledge Base: Configuration Issues