********************************* TOP OF DATA *************************
*
*       The CBDSUDT member in SYS1.SAMPLIB can be used as a model
*       by customers when writing a Unit Data Table (UDT).
*
*       Instructions:
*
*       1) Define a name for your UDT which follows the format
*          CBDECxxx, with xxx between 001 and 256.
*          xxx must match the number used in the name CBDESxxx
*          used for the corresponding UIM.
*          Note: The sample UDT uses the number 255. If you like
*                to use another number, replace the number.
*
*       2) Copy this Sample UDT to a PDS member with the name
*          chosen for your UDT.
*
*       3) Change all strings "CBDEC255" in the UDT to the
*          chosen name.
*
*       4) Change the UDT according to your needs.
*
*       5) Separate the JCL at the end of the UDT,
*          and correct the names in the JCL.
*          Assemble and link-edit your UDT using the JCL.
*
***********************************************************************
*
***** START OF SPECIFICATIONS ****
*
*01* MODULE NAME = CBDEC255
*
*01* DESCRIPTIVE NAME = English Version of the Unit Data Table
*                       for UIM CBDSUIM
*
***********************************************************************
*                                                                     *
*  PROPRIETARY STATEMENT=                                             *
*   LICENSED MATERIALS - PROPERTY OF IBM                              *
*   THIS MODULE IS "RESTRICTED MATERIALS OF IBM"                      *
*   5655-068                                                          *
*   (C) COPYRIGHT IBM CORPORATION 1989, 1995                          *
*                                                                     *
*  END PROPRIETARY STATEMENT                                          *
*                                                                     *
***********************************************************************
*
*01* STATUS = HCSH501
*
*01* FUNCTION =
*      CBDEC255 defines the UIM data (English texts) for the sample
*      UIM CBDES255.
*
*02*   OPERATION = N/A
*
*03*     RECOVERY OPERATION = N/A
*
*01* NOTES =
*
*02*   DEPENDENCIES = None
*
*02*   RESTRICTIONS = None
*
*02*   REGISTER CONVENTIONS = N/A
*
*02*   PATCH LABEL = None
*
*01* MODULE TYPE = Procedure
*
*02*   PROCESSOR = ASSEMBLER-H
*
*02*   MODULE SIZE = For exact size see assembler listing
*
*02*   ATTRIBUTES =
*
*03*     LOCATION = Private
*
*03*     STATE = N/A
*
*03*     AMODE = 31
*
*03*     RMODE = Any
*
*03*     KEY = 8
*
*03*     MODE = N/A
*
*03*     SERIALIZATION = N/A
*
*03*     TYPE = Non Executable
*
*01* ENTRY POINT = CBDEC255
*
*02*   PURPOSE = See FUNCTION
*
*02*   LINKAGE = N/A
*
*03*     CALLERS = N/A
*
*01* INPUT = N/A
*
*02*   ENTRY REGISTERS = N/A
*
*01* OUTPUT = N/A
*
*02*   EXIT REGISTERS = N/A
*
*02*   RETURN CODES = N/A
*
*01* EXIT NORMAL = N/A
*
*01* EXIT ERROR = N/A
*
*01* EXTERNAL REFERENCES =
*
*02*   ROUTINES = N/A
*
*02*   DATA AREAS = N/A
*
*02*   CONTROL-BLOCKS = N/A
*
*01* TABLES = N/A
*
*01* MACROS EXECUTABLE = N/A
*
*01* SERIALIZATION = None
*
*01* MESSAGES = None
*
*01* ABEND CODES = None
*
*01* WAIT STATE CODES = None
*
*01* CHANGE ACTIVITY =
*
*    $H0= HCD   HCSH501 940515 BOEB: Sample UDT for DASD I/O
*
***** END OF SPECIFICATIONS *******************************************
         EJECT
***********************************************************************
*
* Use only CBDZUDT macros to generate the UDT.
*
* The following sequence is required:
*
*   1. UDT header definitions
*   2. Unit definitions
*   3. Parameter definitions
*      (Common and private parameters)
*   4. Feature definitions
*      The features must be defined together
*      and in the same sequence as the corresponding
*      bits in the field UIPMSFEA, set by the UIM.
*   5. Message definitions
*   6. Help definitions
*      UIM specific dialogue field helps.
*      (Not shown in this sample UDT)
*
*----------------------------------------------------------------------
*
***********************************************************************
*  HCD header definition
***********************************************************************
*  The text defined here is shown in "List Installed UIMs"
*----------------------------------------------------------------------
*
         CBDZUDT UDT=CBDEC255,UIM=CBDUC255,                            *
               DESC='UIM FOR 33UU, 93UU'
*
***********************************************************************
*  Unit Definition
***********************************************************************
*  The text defined here is shown in the HCD "View supported
*  device" sub-panel of "List Installed UIMs".
*----------------------------------------------------------------------
*
         CBDZUDT                                                       *
               UNIT='Direct Access Storage Device'
*
***********************************************************************
*  Device parameters
***********************************************************************
*  All OS specific parameters declared in an UIM must be specified
*  also in the corresponding UDT.
*
*  In HCD, a parameter for a device is recognized only if
*  (1) it is described in the UDT that belongs to the UIM defining
*      the device,
*  (2) it is specified as either required or optional parameter in
*      the UIP parameter list for the device.
*
*---------------------------------------------------------------------*
*  Common Parameters                                                  *
*---------------------------------------------------------------------*
*
*  A common parameter is defined by HCD. It has a unique ID in
*  the range between 1 to 32. The parameters that are defined
*  as common are shown in the IODV and UDT data maps.
*
*  Since common parameters are defined within HCD, the allowed
*  values for the parameters are also known to HCD. HCD performs
*  verification checks on the entered values.
*
*  The TEXT keyword allows to provide a description of the parameter.
*  This description is shown on the HCD panel where the OS related
*  parameters of the device are specified.
*
*  The HELP keyword allows to specify a load module which contains
*  help information for the parameter. This help information is
*  displayed when help is requested for the parameter.
*---------------------------------------------------------------------*
*
         CBDZUDT PARA=OFFLINE,                                         *
               TEXT='Device considered online or offline at IPL',      *
               HELP=CBDFP08
         CBDZUDT PARA=DYNAMIC,                                         *
               TEXT='Device supports dynamic configuration',           *
               HELP=CBDED37
*
*---------------------------------------------------------------------*
*  Private Parameters                                                 *
*---------------------------------------------------------------------*
*
*  A private parameter is only known to the UIM to which the
*  UDT belongs to.
*  For a private parameter, an id in the range of 33 through 64 must
*  be specified, together with the parameter name (PARA keyword).
*  The ID of a private parameter need not be unique among the set
*  of installed UIMs. Instead of the parameter name, the ID is
*  stored in the HCD device definition record, and it is used to
*  map the stored parameter to the parameter name with the help
*  of the UDT.
*
*  The TEXT keyword allows to provide a description of the parameter.
*  This description is shown on the HCD panel where the OS related
*  parameters of the device are specified.
*
*  The PARATYPE keyword specifies the type of the parameter value.
*  The type can be one of the following
*
*       NUM       the parameter value is numeric (digits in 0..9)
*       HEX       the parameter value is hexadecimal (digits in 0..F)
*       ALPHANUM  the parameter value is alphanumeric
*       ALPHANUM* the parameter value is alphanumeric or '*'
*       CHAR      the parameter value can contain any character
*       YESNO     the parameter value is 'YES' or 'NO'
*
*  The type specification is used by HCD to perform a syntax check
*  for the parameter value.
*  Additionally, a maximum length can be specified for the
*  parameter value which is also verified by HCD.
*
*  The HELP keyword allows to specify a load module containing
*  help information for the parameter. This help information is
*  displayed when help is requested for the parameter.
*---------------------------------------------------------------------*
*
         CBDZUDT PARA=(DASDPOOL,33),                                   *
               TEXT='DASD pool device belongs to',                     *
               PARATYPE=(ALPHANUM*,4),                                 *
               HELP=CBDED37
*
***********************************************************************
*  Device features                                                    *
***********************************************************************
*  All features declared in a UIM must be specified also in the
*  corresponding UDT. The device features are private to the UIM.
*  They are stored with an ID which is the sequence of the feature
*  description occurrence in the UDT. The UDT is required to map
*  this ID to the feature name and description.
*
*  In HCD a feature for a device is recognized only if
*  (1) it is described in the UDT which belongs to the UIM defining
*      the device,
*  (2) it is specified as a supported feature in the UIP parameter
*      list for the device.
*
*  The TEXT keyword allows to provide a description of the feature.
*  This description is shown on the HCD panel where the OS related
*  parameters and features of a device are specified.
*
*  The HELP keyword allows to specify a load module which contains
*  help information for the feature. This help information is
*  displayed when help for the feature is requested.
*---------------------------------------------------------------------*
*
         CBDZUDT FEAT=ALTCTRL,                                         *
               TEXT='Separate physical control unit path',             *
               HELP=CBDED01
         CBDZUDT FEAT=SHARED,                                          *
               TEXT='Device shared with other systems',                *
               HELP=CBDED02
         CBDZUDT FEAT=SHAREDUP,                                        *
               TEXT='Shared when system physically partitioned',       *
               HELP=CBDED03
*
***********************************************************************
*  Compatible features                                                *
***********************************************************************
*  Compatible feature are features which are accepted by the
*  HCD deck migration function but are no longer stored in the
*  device record in HCD.
*---------------------------------------------------------------------*
*
*        CBDZUDT CFEAT=2-CHANSW
*
***********************************************************************
*  Messages                                                           *
***********************************************************************
*  All messages used in the associated UIM have to be
*  defined in the UDT.
*
*  MID keyword     specifies the message identifier. The value must
*                  be "CBDBnnnI" where nnn is a decimal number in the
*                  range of 800 through 999.
*
*  ID keyword      specifies the parameter associated with the message.
*
*  TEXT keyword    specifies the message text. This text is displayed
*                  when the UIM issues a message.
*                  @n (where n is a decimal number between 1 and 9)
*                  denotes a variable which is passed by the
*                  UIM when issuing the message.
*
*  HELP keyword    specifies a load module which contains the
*                  message explanation. The text of the load module
*                  is displayed when requesting message help in HCD.
*
*                  The help modules referred to in this sample UDT
*                  belong to IBM UDTs.
*---------------------------------------------------------------------*
*
         CBDZUDT MID=CBDB805I,ID=FEATURE,                              *
               TEXT='Features SHARED and SHAREDUP are mutually exclusiv*
               e for device type @1.',                                 *
               HELP=CBDED05
         CBDZUDT MID=CBDB814I,                                         *
               TEXT='The leftmost digit of unit address @1 for device t*
               ype @2 must be even.',                                  *
               HELP=CBDED11
         END

//**********************************************************************
//JJJJJJ    JOB ,NOTIFY=UUUUUU,MSGLEVEL=(1,1),MSGCLASS=H
//ASMH    EXEC PGM=IEV90,REGION=1024K,PARM='LINECNT=55,DECK'
//SYSPRINT  DD SYSOUT=*
//SYSIN     DD DSN=XXXXXXXXXXXXXX(CBDEC255),DISP=SHR
//SYSUT1    DD UNIT=SYSDA,SPACE=(CYL,(5,5)),DISP=(NEW,DELETE)
//SYSPUNCH  DD DSN=&OBJ;(CBDEC255),DISP=(,PASS,DELETE),UNIT=SYSDA,;
//             SPACE=(TRK,(1,5,5))
//SYSGO     DD DUMMY
//SYSLIB    DD DSN=SYS1.AMODGEN,
//             DISP=SHR
//SYSLIN    DD UNIT=SYSDA,SPACE=(TRK,(30,10)),DISP=(NEW,PASS),
//             DSN=&POBJ;
//LKED    EXEC PGM=IEWL,PARM='AMOD=31,LET,LIST,NCAL,RMOD=ANY,XREF',
//             COND=(0,NE)
//SYSPRINT  DD SYSOUT=*,DCB=(RECFM=FB,LRECL=121,BLKSIZE=1210)
//SYSLIN    DD DDNAME=SYSIN
//SYSLMOD   DD DSN=YYYYYYYYYYYYYY(CBDEC255),DISP=SHR
//SYSUT1    DD DISP=(NEW,DELETE),SPACE=(CYL,(5,2)),UNIT=SYSDA
//OBJ       DD DSN=&OBJ;,DISP=(OLD,DELETE);
//SYSIN     DD *
  INCLUDE OBJ(CBDEC255)
  NAME CBDEC255(R)
/*