DDICF Failure with Librarian member

Products

• Datacom
• Librarian
• Datacom/DB

Issue/Introduction

Using DDICF to read a COBOL copybook and create DDUPDATE transactions for a new table works fine when the copybook resides in a PDS but fails when pulling the copybook out of Librarian.

Environment

z/OS

Cause

Librarian / Datacom Interface is not operational.

Resolution

Use the following transaction to invoke DDICF and identify the source library. Only 80-byte records are supported as input to DDICF from any source.

-UTL LIBRARY - Invoking DDICF

When used with the LIB parameter (-UTL LIBRARY,LIB) the Librarian Master file is directly accessed, if the Interface is operational.

To activate the interface,

1. go to Sample Programs, JCL, data, Procedures. 
2. Select the first option in the DataDictionary paragraph : Datadictionary SAMGEN sample assemblies and job
3. Select the DDSAM10 member:

"SAMPLE JCL TO LINK-EDIT THE DDICF MODULE TO THE CUSTOM CUSLIB FOR CA-LIBRARIAN SUPPORT."

Additional Information

For more information about DDICF , see the Datacom/DB documentation: DDICF - Generating Input Transactions .

Note: if the Interface is not operational, the symptom can be unpredictable and most likely output report will be looping with garbage.