SC03 WHILE ACCESSING DBINFPR

[JAGADEESH D]

Hi,

Could you please help with the following error.

IEC999I IFG0TC0A,IFG0TC0B,LJFV470D,STEP010
+IEW2707S DD04 RETRIEVAL FAILED FOR MEMBER DBINFPR FROM DDNAME JOBLIB,
+ CONCATENATION NUMBER 7. COMPONENT BINDER ISSUED RETURN CODE 16 AND
+ REASON CODE DC2AB000, SERVICE TCBTOKEN ISSUED RETURN CODE 00000030
+ AND REASON CODE 00000000.
+IEW2508S 3601 MODULE DBINFPR IDENTIFIED BY DDNAME JOBLIB IS NOT A VALID PROGRAM
+ OBJECT. CODE 0

Not sure why this happens all of a sudden. The DB team performed few changes related to the module DBINRPR / DBINTPR. But the error message is with the module DBINFPR. Could you please help here.

Regards,
Jagadeesh

[Owen Williams]

If your DB team applied maintenance to the Datacom load libraries and those libraries are in the LLA then the Systems Programmers may need to perform an LLA REFRESH for the Datacom load libraries. Otherwise your may have inconsistent load module versions being picked up between the LLA and physical libraries.

Owen Williams Technical Consultant t: [phone]     m: [phone] www.redcentricplc.com

Support  Tel: [phone]     Email: [e-mail]

DISCLAIMER: This message is intended only for the use of the person(s) ("the intended recipient(s)") to whom it is addressed. It may contain information which is privileged, proprietary and/or confidential within the meaning of applicable law. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this message (including any attachments) is strictly prohibited. If you have received this message in error, please contact the sender of this message as soon as possible. The views or opinions expressed in this message are those of the author and may not necessarily be the views held by Redcentric. Redcentric Solutions Limited trading as Redcentric. Registered office: Central House, Beckwith Knowle, Harrogate, HG3 1UG. Registered in England no. 08322856.

[Owen Williams]

Another common cause for these errors is if the maintenance was copied to an existing load library (with replace) and that caused the load library to allocate an additional secondary extent. In that case any existing in-flight jobs or started tasks can receive these errors until the job/stc is stopped and restarted. If "new" jobs are now working fine then this would be the likely cause.

Owen Williams Technical Consultant t: [phone]     m: [phone] www.redcentricplc.com

Support  Tel: [phone]     Email: [e-mail]

DISCLAIMER: This message is intended only for the use of the person(s) ("the intended recipient(s)") to whom it is addressed. It may contain information which is privileged, proprietary and/or confidential within the meaning of applicable law. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this message (including any attachments) is strictly prohibited. If you have received this message in error, please contact the sender of this message as soon as possible. The views or opinions expressed in this message are those of the author and may not necessarily be the views held by Redcentric. Redcentric Solutions Limited trading as Redcentric. Registered office: Central House, Beckwith Knowle, Harrogate, HG3 1UG. Registered in England no. 08322856.