DDICF Failure with Librarian member

Document ID : KB000095100
Last Modified Date : 09/05/2018
Show Technical Document Details
Issue:
I am using DDICF to read a COBOL copybooks and create DDUPDATE transactions for a new table. It works fine when I put the copybook into a PDS, but fails when I try to pull the copybook out of Librarian I thought I had the parms correct according to the doclib. It would be nice to avoid the extra step of pulling the librarian member into a pds. Could you please take a look... 
Environment:
z/os, CA Datacom/DB, CA Librarian
Cause:
Librarian / Datacom Interface was 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 Transaction to Invoke DDICF

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

To activate the interface then have a look at the following URL Sample Programs, JCL, data, Procedures, etc. for

https://support.ca.com/us/product-content/recommended-reading/technical-document-index/use-and-disclosure-of-sample-programs.html 

Select the first option in the CA DataDictionary paragraph :
  1. Datadictionary SAMGEN sample assemblies and job
in that section 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 Datacom/DB documentation:
https://docops.ca.com/ca-datacom/15-1/en/using/ca-datacom-datadictionary-batch-facilities/ddicf-generating-input-transactions/utl-library-invoking-ddicf

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