z/OS DFSMS Access Method Services Commands
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


From a Time Sharing Option Session

z/OS DFSMS Access Method Services Commands
SC23-6846-01

You can use the time sharing option (TSO/E) with VSAM and access method services to:
  • Run access method services functional commands
  • Run a program to call access method services

Each time you enter an access method services command as a TSO/E command, TSO/E builds the appropriate interface information and calls access method services.

You can enter one command at a time. Access method services processes the command completely before TSO/E lets you continue processing. Except for ALLOCATE, all the access method services functional commands are supported in a TSO/E environment.

To use IDCAMS and some of its parameters from TSO/E, your system programmer must update the system by one of these means:
  • Update the IKJTSOxx member of SYS1.PARMLIB. This is the method that IBM® recommends. Add IDCAMS to the list of authorized programs (AUTHPGM). If you want to use SHCDS, SETCACHE, LISTDATA, DEFINE or IMPORT from TSO/E, add them (and abbreviations) to the authorized command list (AUTHCMD).
  • Update the IKJEGSCU CSECT instead of IKJTSOxx, Please see z/OS TSO/E Customization for more information.
The restricted functions performed by access method services that cannot be requested in an unauthorized state are:
  • DEFINE—when the RECATALOG parameter is specified
  • DEFINE—when the define is for an alias of a UCAT
  • DELETE—when the RECOVERY parameter is specified
  • EXPORT—when the object to be exported is a BCS
  • IMPORT—when the object to be imported is a BCS
  • PRINT—when the object to be printed is a catalog
  • LISTDATA—all functions
  • REPRO—when a BCS is copied or merged
  • SETCACHE—all functions
  • SHCDS—all functions
  • VERIFY—when a BCS is to be verified.
When you use TSO/E with access method services, note that:
  • You can use the first characters of a keyword as an abbreviation of the keyword. You must use enough initial characters to make the keyword unique. TRACKS, for example, can be abbreviated TR, TRA, or TRAC, because no other keyword within the same command can be abbreviated in the same way.

    You cannot use some abbreviations (such as REC, RECORD) under TSO/E because the abbreviations do not have enough initial characters to make the keyword unique.

  • When a parameter's value is one or more parenthesized parameter sets, the outer parentheses surrounding the list are always required. For example, if lowkey and highkey form a parameter set that can be repeated several times, then the outer parentheses are required even when just one parameter set is specified; as follows:
    KEYWORD((lowkey  highkey))
  • In TSO/E, a volume serial number can contain alphanumeric characters, national characters ($, @, or #), and hyphens (-). alphabetic, national, numeric, or hyphen only; if any other characters are used, the volume serial number cannot be used as an entry name.
  • A data set name can be placed within quotation marks or not. In TSO/E however, you add a prefix (for example, the user ID) to a name not in quotation marks. The prefix becomes the first qualifier in the name.
  • In TSO/E, you add the necessary qualifiers to the specified name. However, you can be prompted to complete a fully qualified name. You are also prompted to supply any required parameters you have omitted.
  • The modal commands, IF-THEN-ELSE, DO-END, SET, and PARM, are not allowed in TSO/E.
  • In TSO/E, the SYSPRINT data set is not used. The OUTFILE parameter can be used with certain commands to specify a data set to receive access method services output.

Other TSO/E restrictions are noted in Functional Command Syntax.

For details about the format of a displayed catalog entry (resulting from a LISTCAT command) for a TSO/E user, see Interpreting LISTCAT Output Listings.

For details about writing and executing programs with TSO/E, see z/OS TSO/E User's Guide and z/OS TSO/E Command Reference.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014