Format and explanation of data

Figure 1. File allocation report: standard format

PAGE nnnn  - NOW SET TO zzzzzz ZONE nnnnnnn  DATE mm/dd/yy TIME hh:mm:ss SMP/E 36.nn SMPRPT OUTPUT

SMP/E xxxxxxxx FILE ALLOCATION REPORT

ZONE    DDNAME   DDDEFNAM SMPDDNAM TYPE    --------------DATA SET OR PATH-------------- VOLSER UNIT     STATUS

aaaaaaa bbbbbbbb cccccccc dddddddd eeeeeee ffffffffffffffffffffffffffffffffffffffffffff gggggg hhhhhhhh iii
aaaaaaa bbbbbbbb cccccccc dddddddd eeeeeee ffffffffffffffffffffffffffffffffffffffffffff gggggg hhhhhhhh iii
aaaaaaa bbbbbbbb cccccccc dddddddd eeeeeee ffffffffffffffffffffffffffffffffffffffffffff gggggg hhhhhhhh iii
aaaaaaa bbbbbbbb cccccccc dddddddd eeeeeee ffffffffffffffffffffffffffffffffffffffffffff gggggg hhhhhhhh iii
aaaaaaa bbbbbbbb cccccccc dddddddd eeeeeee ffffffffffffffffffffffffffffffffffffffffffff gggggg hhhhhhhh iii
aaaaaaa bbbbbbbb cccccccc dddddddd eeeeeee ffffffffffffffffffffffffffffffffffffffffffff gggggg hhhhhhhh iii

These are the fields in the report:

xxxxxxx

is the SMP/E command being processed.

ZONE

For the APPLY and RESTORE commands, the ZONE field contains the name of the cross-zone whose DDDEFs have been used for the allocation of the library. An SMP-generated DD is used instead of the DDNAME to keep all currently allocated DDs unique.
For the LINK MODULE command, the ZONE field contains the name of the FROMZONE or DLIB zone related to the FROMZONE whose DDDEF has been used to allocate the library.

DDNAME

is the ddname of the DD statement used. It can be either a user-specified ddname or one that was generated by SMP/E.

DDDEFNAM

is the name of the DDDEF entry that was used to allocate the DDNAME data set. This field is filled in only if SMP/E dynamically allocated the DD statement. It is blank for:

Background processing when the JCL supplied a DD statement
Foreground processing when the data set was preallocated using the TSO ALLOCATE command

The SMPPTS entry in the sample report is an example of a DD statement specified by the user (its DDDEFNAM field is blank).

SMPDDNAM

is filled in only for concatenated DD statements that were dynamically allocated by SMP/E. When a DDDEF entry lists data sets to be concatenated, SMP/E dynamically allocates the individual members and assigns each data set a unique ddname. This name is shown in the SMPDDNAM field. SMP/E then requests that these individual ddnames be concatenated and assigned the ddname indicated in the DDNAME field. The SYSLIB entry in the sample report is an example of concatenated DD statements.

Note:

For concatenated DD statements specified in the JCL, only the information from the first concatenated library is displayed.
This field is also used to show the data sets in a SYSLIB allocation for a load module, as indicated by the CALLLIBS subentry list in the corresponding LMOD entry. Each ddname in the CALLLIBS list is displayed, along with the information from its corresponding DDDEF entry and its SMP/E-generated ddname. When the CALLLIBS subentry list contains more than one name, SMP/E allocates them as a concatenation and gives the concatenation a generated ddname.

TYPE

is either the type of data set that was allocated or the reason the data set was not allocated. TYPE may also be set when more than one type of information is being generated for a file. In this case, the TYPE field is used to qualify the information for the file.

ERROR

An error occurred when SMP/E tried to dynamically allocate the specified ddname. See the error messages in SMPOUT to determine the cause of the error.

NODDF

There was no DDDEF entry in the current zone; so SMP/E could not dynamically allocate the requested DD statement.

The SMPRPT entry in the sample report is an example of a DD statement that was not found. In this case, because SMP/E could not allocate the SMPRPT DD statement, it had to write all reports to the SMPOUT DD statement.

NTFND

The JCL did not contain the required DD statement. SMP/E tries to dynamically allocate the DD statement using the DDDEF entries.

PATH

The DATA SET OR PATH field of the report is filled in with the path in a UNIX file system to which the file was allocated.

PATHHFS

The DATA SET OR PATH field of the report is filled in with the name of the HFS data set containing the path to which the file was allocated.

The PATHHFS line is generated for all commands in which a path in a UNIX file system has been allocated.

PERM

The DD statement specified a permanent data set.

SYMHFS

The DATA SET OR PATH field of the report is filled in with the name of the HFS data set containing a symbolic link for an element or load module that was updated in the path to which the file was allocated.

Any SYMHFS lines will follow the PATHHFS line for an allocated file.

The SYMHFS lines will only be generated during APPLY, LINK LMOD, LINK MODULE, or RESTORE processing. In APPLY, LINK LMOD, LINK MODULE, or RESTORE, the elements and load modules updated or deleted from libraries allocated to a path will now be tracked. A list of all symbolic links for these elements or load modules will be derived. The physical HFS data set containing the symbolic link is then derived. A list of data sets containing symbolic links is thus determined. Any duplicates are removed from the list. In addition, if the data set name matches the data set name in the PATHHFS line it is also removed from the list. A SYMHFS line is written to the report for all remaining data sets.

SYSIO

The DD statement specified a SYSIN or SYSOUT data set.

The SMPOUT entry in the sample report is an example of a SYSIO data set. The data set name in this sample is the temporary JES2 data set name (shown as JES2.A.B…).

TEMP

The DD statement specified a temporary data set.

The entries for SMPWRK1 through SMPWRK6 in the sample report are examples of temporary data sets allocated by SMP/E.

VIO

The DD statement specified is a VIO data set.

The entries for SYSUT1 through SYSUT4 in the sample report are examples of VIO data sets specified by the user; their DDDEFNAM fields are blank.

DATA SET OR PATH

is the name of the data set or path specified in the DDDEF entry or in the JCL.

For data sets, the full data set name (up to 44 characters) is displayed.
For concatenated DD statements specified in the JCL, only the information from the first concatenated library is displayed.
For paths, the full pathname (up to 255 characters) is displayed. The pathname is enclosed by apostrophes. If the pathname plus the enclosing apostrophes is greater than 44 characters, the pathname spans several lines.

VOLSER

identifies the volume specified in the DDDEF entry, the JCL, or the catalog.

UNIT

identifies the unit where the data set resides. This field is filled in if SMP/E dynamically allocated the DD statement and the DDDEF entry contained the unit information. Otherwise, this field is blank.

STATUS

is the status of the data set: NEW, OLD, MOD, or SHR.