We've found a problem with the Create Logical File (CRTLF) command. If we specify a library name in the Library element of the Physical file data members (DTAMBRS) parameter (see 7), the system ignores it. You can specify the library where the physical file resides in the PFILE keyword of the logical file's DDS. However, this method requires you to change source code if you want to use a different library. If a library is not specified in the PFILE keyword, the library list is used to locate the physical file. If the physical file is not found in the library list, the logical file will not be created, even if the library is specified in the Library element of CRTLF's DTAMBRS parameter.
We've found a problem with the Create Logical File (CRTLF) command. If we specify a library name in the Library element of the Physical file data members (DTAMBRS) parameter (see Figure 7), the system ignores it. You can specify the library where the physical file resides in the PFILE keyword of the logical file's DDS. However, this method requires you to change source code if you want to use a different library. If a library is not specified in the PFILE keyword, the library list is used to locate the physical file. If the physical file is not found in the library list, the logical file will not be created, even if the library is specified in the Library element of CRTLF's DTAMBRS parameter.
We feel that allowing the physical file's library parameter to be entered but never used when executing CRTLF is misleading. We contacted IBM about this situation, but at that time, they had no plans to change the command's logic or the command's prompt panel.
? Terry Bridenbaugh, Rogenia Chaffin, Joe Dennis
LATEST COMMENTS
MC Press Online