EXEC naming conventions

The naming convention for the sample solutions EXECs uses the following format:

gffnnnl

where

Placeholder

Description

g

is the first letter of the group (for example, M for MVS)

ff

is a 2-character abbreviation for the functional area within the group where

  • AM: represents ACCESS METHODS*
  • ER: represents ERROR RECOVERY*
  • IN: represents INFO SYS/MANAGEMENT
  • J2: represents JES2
  • J3: represents JES3*
  • MN: represents MONITORS
  • PE: represents PERFORMANCE*
  • ST: represents STORAGE SUBSYSTEMS*
  • UT: represents UTILITIES
  • VT: represents VTAM/NCP

nnn

is a sequence from 001 to 999

l

is the language of the particular EXEC (for example, X for REXX or C for CLIST)


Related topic

Sample-solutions

The following three categories of EXECs do not follow this naming convention:

  • operator-initiated EXECs

Operator-initiated EXECs are executed as a result of an operator command.

  • text ID-driven EXECs

Text ID-driven EXECs are executed as a result of a WTO or WTOR. The names for Text ID-driven EXECs are the text IDs.

  • SYSPROG Services EXECs

SYSPROG Services EXECs are the command interfaces to SYSPROG Services. When a sample solution requires more data to complete its analysis, the SYSPROG Services EXECs can be used to provide concise and pertinent data.

The sample solutions EXECs are distributed with a documentation box. Refer to Documentation-boxes for an example of the documentation box.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*