1469 error-status in an IDMS batch job
search cancel

1469 error-status in an IDMS batch job

book

Article ID: 95071

calendar_today

Updated On:

Products

IDMS IDMS - Database

Issue/Introduction

Why would a batch to CV job receive error-status 1469 upon issuing a BIND RUN-UNIT?

Environment

Release: All supported releases.

Resolution

If a batch program accessing an IDMS CV using SYSCTL or CICS program receives error-ststaus 1469 for a BIND RUN-UNIT DML, it means the connection to the CV was denied.

There can be several reasons for this including that the IDMS CV in question is not active. If that is the case the CV should be brought up and the program retried.

Another reason is that CAIRIM was refreshed as is described in the following articles:
UCF Batch job gets 1469 Back-end system is not active
1469 in all batch and CICS

If the CV is up and SVC was not refreshed, the 1469 for BIND RUN-UNIT from a batch CV job or CICS program may indicate an automatic signon failure. The IDMS CV joblog will have the message that indicates the signon failure for the external program.

DC201006 Vnn T1 CV-Status BE-TaskID Pri FE - ID1 FE - ID2 FE TaskCD FE USERID FE - ID3 
DC201006 Vnn T1 ABRT SNON .. 20     100 BATCBULK CV02DA     IDMSBCF    userid 8CA006E3 

This message will show the userid that was passed from the front-end program. If RESTYPE=SGON is secured, the userid shown is not defined or has not been granted the signon privilege to the IDMS System.

 If the userid shows as PUBLIC, it is possible that an invalid USRIDXIT is being used that passes PUBLIC as the userid. The sample USRIDXIT source delivered in CAGJSRC contains the comment 

   THE 'USERID' MUST --> NOT <-- BE CODED AS 'PUBLIC' 

If opsys is VSE and there is no external security manager, USRIDXIT is required to provide a valid userid for batch, so the 1469 could be an indication that the proper USRIDXIT has not been implemented. 

The reason can also be a TASK security violation. The CV joblog would show something like:

DC201006 Vnn T1 CV-Status  BE-TaskID Pri FE - ID1 FE - ID2 FE    TaskCD     FE USERID      FE - ID3
DC201006 Vnn T1 ABRT STDE      nnnnn 100 BATCBULK <Fe-id>        IDMSDDDL   <userid>       nnnnnnnn

The IDMS DC LOG would have something like this:

DC021102 V3 SECURITY VIOLATION BY USER <userid>.
            ACCESS TO RESOURCE IDMSDDDL DENIED.

Additional Information