Discovery Library file naming standards

All files in the DLFS must comply with the Discovery Library file name standards:
appcode.hostname.timestamp.refresh.xml
where:
  • AppCode= the DLA Application Code
    • ZOSDISC320ALL for ZOSALL books
    • ZOSDISC320BASE for ZOSBASE books
    • ZOSDISC320TASK for ZOSTASK books
    • ZOSDISC320DB2® for Db2® subsystem books
    • ZOSDISC320IMS for IMS Subsystem books
    • ZOSDISC320MQ for MQ Subsystem books
    • ZOSDISC320CICS® for CICS Region Subsystem books
    • ZOSDISC320WAS for WebSphere® Application Server books
  • Hostname= the MSS Hostname specified in the IdML MSSName, which the z/OS® DLA populates in the format member@fqdn
  • timestamp= the timestamp specified in the IdML create or IdML refresh clauses.
  • .refresh= .refresh if the IdML has a refresh clause.
  • File name conversions are stored in @FTPCHGG members.
Discovery Library standards also say that files being transferred to the DLFS include a suffix of .partial. When transfer is complete, the file is renamed to remove the suffix. This file name convention is not applicable on z/OS because of a 44-character limit for the data set name and a restriction on symbols used. So the z/OS DLA generates FTP statements to transfer the IdML members and renames them to the appropriate Discovery Library format, for example:
PUT IMP1CTL
ZOSDISC210IMS.IMP1CTL@pthomo1.au.ibm.com.2006-09-04T02.07.17Z.xml.partial
REN ZOSDISC210IMS.IMP1CTL@pthomo1.au.ibm.com.2006-09-04T02.07.17Z.xml.partial
ZOSDISC210IMS.IMP1CTL@pthomo1.au.ibm.com.2006-09-04T02.07.17Z.xml

The mapping of z/OS members to longer file names that meet Discovery Library standards is specified in members @FTPCHGG and @FTPCHGP, which are written to the same directory as the books.