CA OPS/MVS release 13.0OPSOSF start up failed due to a DBCS character detection.

Document ID : KB000094131
Last Modified Date : 02/05/2018
Show Technical Document Details
Issue:
When CA OPS/MVS is trying to start OPSOSF, the job is failing with JCL error below:

2 //STARTING EXEC OPSOSF,SSID=OPSS
2 IEFC612I PROCEDURE OPSOSF WAS NOT FOUND

*OPS3101S Message number 0030 not found - OPINAS+X'00000A28'
IEF196I OPS3101S Message number 0030 not found - OPINAS+X'00000A28'
OPS0040I IKJ56644I NO VALID TSO USERID, DEFAULT USER ATTRIBUTES USED
IEF196I OPS0040I IKJ56644I NO VALID TSO USERID, DEFAULT USER ATTRIBUTES
IEF196I USED OPS0040I IKJ79043I STMT 49 OTHER THAN DBCS CHARACTER FOUND IN A DBCS STRING
Environment:
CA OPS/MVS Event Management and Automation release 13.0
z/OS
Cause:
DBCS is enabled on this LPAR and a character other than DBCS detected.
Resolution:
This problem is likely an issue with the LPAR environment. Check to see if you have DBCS enabled on the LPAR where the IKJ79043I error occurred. Correct the LPAR environment.