JES3

With few exceptions, the use of the IBM® 3590/3592 tape subsystem as an execution device in a JES3 complex is transparent to JES3. You must define the devices to JES3 in the initialization stream for JES3 to manage the devices. Once defined, JES3 manages the IBM 3590/3592 drives in the same way that it manages other tape devices.

Note: All IBM tape devices since the 3590 Model B1x emulate the 3590 Model B1x and use the generic unit name 3590-1, including all 3590 and 3592 devices. Esoteric names are required to differentiate IBM 3590/3592 tape subsystem models.
To update the JES3 Initialization stream follow the steps described below:
  1. Specify the generic unit name and any esoteric unit names by which the IBM 3590 drives may be requested; use one or more SETNAME statements.
  2. Specify these unit names on HWSNAME statements, if you are using High Watermark Setup, or catalog overrides--for example, if a unit name specified on JCL is more restrictive than the IBM 3590/3592 generic unit name of 3590-1. In these cases, the JCL unit name will override the unit name in the catalog.

    The rules for specifying the IBM 3590/3592 unit names on these statements are the same as for other device types. For example, each unit name must appear as the primary unit name on one HWSNAME statement.

    Note: Because IBM 3590/3592 is not compatible with other tape device types, the alternate unit names that follow the primary name must not contain any other device type.
  3. Define the IBM 3590/3592 drives using DEVICE statements. If the JUNIT parameter is specified, the DTYPE should be specified as TA435901.

    To request an IBM 3590/3592 drive for the DUMP Job DSP, you may specify TA4 or TA435901 or the device address on the IN= or OUT= parameter. You can request compaction using the existing MOD= key word. Do not use the DEN= key word: it is ignored except for a warning message because the IBM 3590/3592 writes a single density tape.

    Other JES3 Tape Dynamic Support Programs (DSPs) such as Tape Label or Tape-to-tape do not support the IBM 3590/3592 devices.

  4. If the IBM 3590/3592 tape subsystems are installed in an IBM tape library, you must define the following esoteric names:
    • LDBsssss, which includes all IBM 3590 devices in the library with library ID sssss.
    • LDG3591, which includes all IBM 3590 devices in any library.
    • LDCsssss, which includes all IBM 3590 Model E1x devices in the library with library ID sssss.
    • LDG359C, which includes all IBM 3590 Model E1x devices in any library.
    • LDFsssss, which includes all IBM 3590 Model H1x devices in the library with library ID sssss.
    • LDG359F, which includes all IBM 3590 Model H1x devices in any library.
    • LDJsssss, which includes all IBM 3592 Model J1A devices in the library with library ID sssss.
    • LDG359J, which includes all IBM 3592 Model J1A devices in any library.
    • LDKsssss, which includes all IBM 3592 Model E05 devices in the library with library ID sssss.
    • LDG359K, which includes all IBM 3592 Model E05 devices in any library.
    • LDLsssss, which includes all IBM 3592 Model E05e (encryption capable) devices in the library with library ID sssss.
    • LDG359L, which includes all IBM 3592 Model E05e (encryption capable) devices in any library.
    • LDMsssss, which includes all IBM 3592 Model E06 devices in the library with library ID sssss.
    • LDG359M, which includes all IBM 3592 Model E06 devices in any library.
    • LDNsssss, which includes all IBM 3592 Model E07 devices in the library with library ID sssss.
    • LDG359N, which includes all IBM 3592 Model E07 devices in any library.
    Note: The name 3590-1 and any nonlibrary esoteric unit name must not include any library devices.

Figure 1 shows the sample JES3 definitions for an IBM tape library with one string of four 3590 Model B1x tape drives. The library name in this example is F4006.

Figure 1. Sample JES3 definitions for IBM 3590 Model B1x with an IBM tape library
  SETNAME,XTYPE=LB135901,NAMES=(LDGW3495,LDGF4006,LDG3591,LDBF4006)
                                  |        |        |       |
                                  V        V        V       V
                              Complex   Library   Complex Library
                              Wide      Specific  Wide    Specific
                              Library   Library   Device   Device
                              Name      Name      Name     Name

  DEVICE,XTYPE=(LB135901,TA),XUNIT=(500,SY1,TAP,OFF)
  DEVICE,XTYPE=(LB135901,TA),XUNIT=(501,SY1,TAP,OFF)
  DEVICE,XTYPE=(LB135901,TA),XUNIT=(502,SY1,TAP,OFF)
  DEVICE,XTYPE=(LB135901,TA),XUNIT=(503,SY1,TAP,OFF)
  HWSNAME,TYPE=(LDGW3495,LDGF4006,LDG3591,LDBf4006)
  HWSNAME,TYPE=(LDGF4006,LDG3591,LDBF4006,LDGW3495)
  HWSNAME,TYPE=(LDG3591,LDBF4006,LDGW3495,LDGF4006)
  HWSNAME,TYPE=(LDBF4006,LDGW3495,LDGF4006,LDG3591)

You could also define the entire library with one DEVICE statement by defining it as follows: DEVICE,XTYPE=(LB135901,TA),XUNIT=(500,*ALL,TAP,OFF),NUMDEV=4

The complex-wide library name is always LDGW3495, regardless of the IBM tape library device type and model, and includes all IBM tape libraries.
Note: IBM 3590/3592 drives installed in an IBM tape library cannot be used to as support units for JES3 DSPs. Therefore, do not specify DTYPE, JUNIT, and JNAME parameters on the DEVICE statement. No check is made during initialization to prevent library drives from being defined as support units, and no check is made to prevent the drives from being allocated to a DSP if they are defined. Any attempt to call a tape DSP by requesting an IBM tape library fails because the DSP is unable to allocate an IBM tape library drive.

Job Entry Subsystem 3 (JES3), an MVS™ subsystem, manages resources and workflow before and after jobs are processed.

Parent topic: JES3 support for IBM tape libraries