dlbl ijsysuc clear
or, you can assign the ddname IJSYSUC to some other catalog.
clear the ddname for IJSYSUC, then the master catalog becomes
catalog.
If you
the job When you define passwords for VSAM catalogs in CMS, or when you use CMS to access VSAM catalogs that have passwords associated with them, you
must supply the password from your terminal when the AMSERV command
executes. The message that you receive to prompt you for the password
is the same message you receive when you execute access method services:
4221A ATTEMPT 1 OF 2. ENTER PASSWORD FOR JOE AMSERV FILE catalog When you enter the proper password, AMSERV continues execution.
DEFINING AND ALLOCATING SPACE FOR VSAM FILES You can use CMS AMSERV to allocate additional data spaces for VSAM. To
use the DEFINE SPACE control statement, you must have defined either the
master catalog or a user catalog which will control the space, and you
must have the volume or volumes on which the space is to be allocated mounted and accessed.
For example, suppose you have an OS 3330 disk attached to your
virtual machine at virtual address 255. After accessing the disk and
determining the free space on it, you could create a file named SPACE AMSERV: DEFINE SPACE -
(FILE (FILE1) - TRACKS (1900) - VOLUME (123456) - CATALOG (PRIVATE.CAT2 CAT2) )
To execute this AMSERV file, you must define PRIVATE.CAT2 using the
ddname CAT2, and then define the ddname for the file:
access 255 c
dlbl cat2 c dsn private cat2 {vsam
dlbl file1 c (extent cat cat2 You do not need to enter a data prompts you for the extents of
specifications:
set name to define the space. When CMS the space, you can enter the extent DMSDLB331R ENTER EXTENT SPECIFICATIONS: 190 1900 When you define space for VSAM, you should be sure that the VOLUMES parameter and the space allocation parameter (whether CYLINDER, TRACKS, or RECORDS) in the AMSERV file agree with the track information you
provide in the DLBL command. 202 IBM VM/370 CMS User's Guide

March 30, 1919 When you are specifying extents for a master catalog, data space, or
unique file, you can specify up to 16 extents on a volume for a
particular space. When prompted by eMS for the extents, you aust separate the different extents by commas, or place them on different
lines. To specify a range of extents in the above example, you could
enter:
dlbl file1 c (extent 190 190, 510 190, 1900 1520 (null line)
or --
dlbl file1 c (extent 190 190 570 190 1900 1520 (null line)
Again, the first number entered for each extent represents the relative
track for the beginning of the extent and the second number indicates
the number of tracks. You can define spaces that span up to nine volumes for VSAM files; all
of the volumes must be accessed and assigned when you issue the DLBL command to define or identify the data space. You should remember, though, that if you are using IBSERV and you do
not use the PRINT option, you must have a read/write CBS disk so that AMSERV can write the output LISTING file.
If you are defining a new multivolume data sFace or unique cluster,
you must specify the extents on each volume that the data is to occupy (starting track and number of tracks), followed by the disk mode letter
at which the disk is assigned:
access 135 b
access 136 c
access 131 d
dlbl newfile b (extent DMSDLB331R ENTER EXTENT SPECIFICATIONS: 100 60 b, 400 80 b, 60 40 d , 2000 100 c
(null line)
If you enter more than one extent on the same line, the extents must be
separated by commas; if you enter a comma at the end of a line, it is
ignored. Different extents for the same volume must be entered
consecutively. Note that in this example, the extent information is for
2314 disks and that these extents are also on cylinder toundaries. When you enter multivolume extents, you do not have to enter a mode letter for those extents on the disk identified in the DLBL command. For the extents on disk B in the above example, you could enter:
Section 10. Using Access Method Services and VSIB 203