z/VSE JCL › Utility Statements › FORMAT

FORMAT

File assignments for the batch command facility (z/VSE)

To format a new database file:

// DLBL    userdb,'user.userdb',,tt
// EXTENT  SYSnnn,nnnnnn,,,ssss,rrrr
// ASSGN   SYSnnn,DISK,VOL=vvvvvv,SHR

To reformat an existing database file:

// DLBL    userdb,'user.userdb',,tt
// EXTENT  SYSnnn,nnnnnn
// ASSGN   SYSnnn,DISK,VOL=vvvvvv,SHR

To format a new disk journal file:

// DLBL    j1jrnl,'idms.j1jrnl',,SD
// EXTENT  SYSnnn,nnnnnn,,,ssss,rrrr
// ASSGN   SYSnnn,DISK,VOL=vvvvvv,SHR

To reformat an existing disk journal file:

// DLBL    j1jrnl,'idms.j1jrnl',,SD
// EXTENT  SYSnnn,nnnnnn
// ASSGN   SYSnnn,DISK,VOL=vvvvvv,SHR

Additional database and journal file assignments, as required

To format a new SYSTRK file:

// DLBL ffff.,'idms.systrk1',,xx
// EXTENT SYSnnn,nnnnnn,,,ssss,rrrr
// ASSGN SYSnnn,DISK,VOL=vvvvvv,SHR

To reformat an existing SYSTRK file:

// DLBL ffff,'idms.systrk1',,xx
// EXTENT SYSnnn,nnnnnn
// ASSGN SYSnnn,DISK,VOL=vvvvvv,SHR

Multiple extents

You can format a CA IDMS/DB VSAM file with multiple extents under z/VSE. However, you cannot format a BDAM file with multiple extents.

The SIZE parameter on the EXEC statement

The SIZE parameter on the EXEC statement enables the IBM rotational sensing (RPS) feature. When formatting CA IDMS/DB VSAM files, you should specify SIZE=AUTO on the EXEC statement for IDMSBCF.

Do not use the SIZE parameter at all when formatting BDAM files or files allocated on 3344 disk devices with RPS implemented within the hardware. When you use the SIZE parameter in these cases, CA IDMS/DB cannot access the required current updated copy of the DTF.

Central version

To execute FORMAT AREA or FORMAT SEGMENT under the central version:

• Remove the TLBL and ASSGN statements for the tape journal file from the previous JCL.
• Insert the following statement:

  // DLBL SYSCTL,file-id,0,SD
  // EXTENT SYSnnn,vvvvvv,1,0,1,1
  // ASSGN SYSnnn,DISK,VOL=vvvvvv,SHR