The DSNMAPxx.ini file maps data sets to path names and path names to data set attributes. The suffixes for the DSNMAPxx.ini files are specified in the DSNMAP parameter of the IEASYSxx.ini file.
Each DSNMAPxx.ini file may contain multiple statements and comments. A comment is allowed whenever a blank is allowed. Comments start with /* and end with */. Comments may not be nested.
Each statement must start on a separate line from previous statements. Each statement has a type and may be followed by up to 100 parameters. More than one parameter may be specified on each line of the statement. Parameters may be continued on to a new line by coding the parameter up to column 72 and continuing in column 1 of the next line. Each parameter value must be enclosed in parentheses which must immediately follow the parameter name. The statement types and parameters are:
The data set attributes are applied to any DD statement with a matching data set name that are not coded with the attribute. If more than one DSNMAP statement is specified for the same data set, the data set attributes on the last matching DSNMAP statement are used. If there also are matching DSATTR statements for the PATH, the DSATTR data set attributes are used if they are not provided in the DD statement or the DSNMAP statement.
DSNMAP entries for load libraries must be specified with FILEDATA(BINDER). FILEDATA(BINDER) specifies that the simulated partitioned data set contains executable programs and that it may be accessed only through the LINK(X), LOAD or XCTL(X) services.
There must be a DSNMAP entry for all data sets listed in the LNKLSTxx.ini, LPALSTxx.ini and PROGxx.ini configuration files as well as any partitioned data sets referenced in JCL DD statements. DSNMAP entries for these data sets must contain either &M or &m in the PATH parameter value. The &M or &m marks the position in the path name where the member name will be substituted when the Tachyon Operating System searches the library for a member. The &M or &m must follow the directory name in the path and may be followed by a path name extension.
The Tachyon Operating System automatically creates entries for SYS1.NUCLEUS, SYS1.LINKLIB and SYS1.LPALIB unless they are specified in the DSNMAPxx.ini configuration files. These default entries are shown in the DSNMAPxx.ini sample below.
One or more PATH parameters must be specified on each CATALOG statement. The value of each PATH parameter must be the name of a directory. The order that the PATH parameters are specified determines the order that the directories are searched.
When a data set is named in a DD statement without a PATH parameter, the Tachyon Operating System first searches for the data set in the DSNMAP statements. If the data set name is not found in any DSNMAP statement, the Tachyon Operating System appends ".CAT" to the data set name and searches the CATALOG PATH directories in the specified order for the catalog information file.
After you run several jobs, you may find that the spool directory is cluttered with SYSOUT files. You may want to consider deleting these files periodically. You should not delete the jesjobno.ini file since it keeps track of the next job number. If this file is deleted, the job number will be reset to 1.
/* Sample DSNMAP00.ini file */ DSATTR EXT(txt) EXT(ini) RECFM(FB) LRECL(80) BLKSIZE(3200) FILEDATA(TEXT) DSNMAP DSN(SYS1.DUMP) PATH(&SYSDIR\files\sys1dump.txt) RECFM(VA) LRECL(121) BLKSIZE(125) DSNMAP DSN(SYS1.PARMLIB) PATH(&SYSDIR\&m.ini) SPOOL PATH(&SYSDIR\spool) TEMP PATH(C:\temp) /* Default entries ... */ DSNMAP DSN(SYS1.NUCLEUS) PATH(&SYSDIR\&m.nuc) RECFM(U) LRECL(18000) BLKSIZE(18000) FILEDATA(BINDER) DSNMAP DSN(SYS1.LINKLIB) PATH(&SYSDIR\&m.pgm) RECFM(U) LRECL(18000) BLKSIZE(18000) FILEDATA(BINDER) DSNMAP DSN(SYS1.LPALIB) PATH(&SYSDIR\&m.lpa) RECFM(U) LRECL(18000) BLKSIZE(18000) FILEDATA(BINDER) CATALOG PATH(C:\vsam) PATH(.) PATH(&SYSDIR\vsam)