Access Method Services Not Supported in CMS
In
CMS, an OS user is a user that has not issued the command:
SET DOS ON (VSAM)
OS users can use all of the Access Method Services functions that
are supported by VSE/VSAM, with the following exceptions:
- Non-VSAM data sets with data formats that are not supported by CMS/DOS (for example, BDAM and ISAM files are not supported).
- The SHAREOPTIONS operand is not supported for cross system or cross partition sharing in CMS/DOS (that is, DASD sharing is not supported).
- The EXCEPTIONEXIT operand of DEFINE CLUSTER or DEFINE ALTERNATE INDEX is not supported under CMS (both CMS/DOS and OS users).
- Do not use the AUTHORIZATION (entrypoint) operand in the DEFINE and ALTER commands unless your own authorization routine exists on the DOS core image library, the private core image library, or in a CMS DOSLIB file. In addition, results are unpredictable if your authorization routine issues an OS SVC instruction.
- The OS Access Method Services GRAPHICS TABLE options and the TEST option of the PARM command are not supported.
- The file name in the FILE (filename) operands is limited to seven characters. If an eighth character is specified, it is ignored.
- The OS access method services CNVTCAT and CHKLIST commands are not supported in VSE/VSAM access method services. In addition, all OS access method services commands that support the 3850 Mass Storage System are not supported in DOS/VS access method services.
- Table 1 is a list of OS operands, by control statement, that are not supported by the CMS interface to VSE/VSAM Access Method Services.
If any of the unsupported operands or commands in Table 1 are specified, the AMSERV command terminates and displays an appropriate error message.
OS ACCESS METHOD SERVICES CONTROL STATEMENT | OPERANDS NOT SUPPORTED IN CMS |
---|---|
ALTER | EMPTY/NOEMPTY SCRATCH/NOSCRATCH DESTAGEWAIT/NODESTAGEWAIT STAGE/BIND/CYLINDERFAULT |
DEFINE | ALIAS EMPTY/NOEMPTY GENERATIONDATAGROUP PAGESPACE SCRATCH/NOSCRATCH DESTAGEWAIT/NODESTAGEWAIT STAGE/BIND/CYLINDERFAULT TO/FOR/OWNER1 |
DELETE | ALIAS GENERATIONDATAGROUP PAGESPACE |
EXPORT | OUTDATASET |
IMPORT | INDATASET OUTDATASET IMPORTA |
LISTCAT | ALIAS GENERATIONDATAGROUP LEVEL OUTFILE2 PAGESPACE |
INDATASET OUTFILE2 | |
REPRO | INDATASET OUTDATASET |
When you use the PRINT, EXPORT, IMPORT, IMPORTRA, EXPORTRA, and REPRO control statements for sequential access method (SAM) data sets, you must specify the ENVIRONMENT operand with the required DOS options (that is, PRIME DATA DEVICE, BLOCKSIZE, RECORDSIZE, or RECORDFORMAT). You must have previously issued a DLBL for the SAM file.
AMSERV can write SAM data sets only to a CMS disk or directory, but can read them from DOS, OS, or CMS disks or directories.
1 The TO/FOR/OWNER operands are supported for the access
method services interface, but are not supported for the DEFINE NONVSAM
control statement.
2 The OUTFILE operand is supported by the access method
services interface, but is not supported for the LISTCAT and PRINT
control statements.