Operations › VSE/ESA Environment › File Processing Alternate Method

File Processing Alternate Method

Occasionally you will receive a message that a file is not VSAM. The message indicates that the dataset will be processed SAM instead of VSAM because CA IDMS/DB Analyzer was not able to find the dataset in the VSAM catalog. The allocation will not affect processing results.

• sort.work1/sort.work4— The file ID of each of the four sort work files.
• volser— The volume serial number or generic assignment of the disk volume on which the file, specified in the preceding DLBL statement, resides.
• rel-trk-blk— Relative track or relative block numbers: the starting position on the DASD for storage of the work file specified in the previous statement.
• amount— The space allocation you need to store the file specified in the previous statement.
• dbfil01/dbfilnn— The file name of each of the database files to be accessed.
• user.dbfil01/user.dbfilnn — The file ID of each of the database files to be accessed.
• SYSnnn— The programmer logical units of the database files to be accessed.
• dbnlyzr.file1— The file ID assigned to your "new" statistics file.
• dbnlyzr.file2— The file ID assigned to your "old" statistics file. Only statistics from a single release of CA IDMS/DB Analyzer can be compared.
• dbnlyzr.file3— The file ID assigned to your LDEL file.
• #k— The number of kilobytes of storage to be made available to the sort phase.
• tool.loadlib— The data set name of the library into which you installed CA IDMS/DB Analyzer.
• idms.loadlib— The data set name of the library in which your DMCL and subschema reside.
• TOOL.sublib/IDMS.sublib—The sublibrary names into which you installed the CA IDMS tools and CA IDMS products.