II07348: INFORMATIONAL APAR FOR HCD INSTALL AND USAGE PROBLEMS. *** SEE II08750 FOR OTHER HCD RELATED INFO ***

APAR status

• Closed as canceled.

Error description

• The purpose of this INFO APAR is to document HCD USAGE
  situations and the EXTERNAL SYMPTOMS for SEARCHABILITY by HCD
  support groups (i.e.,Level1,Level2).
  **** see INFO APAR II08750 for more info ****
  ****************************************************************
  D/T3995 model 15x. The model 15x emulates a 3390 and should be
  defined in HCD as a 3390 attached to a 3990 CU. For model 13x
  see II06097.
  ****************************************************************
  When attempting to use GRS w/an MVS 420 system using an ESCON
  channel, HCD/MVS will NOT accept BCTC on the 420 system.
  For this case gen the chpid type as CTC on the lpar
  that is higher than MVS 420 and use BCTC for the IODEVICE.
  On the lpar that is MVS 4.2 gen the chpid type as CNC.
  On this 420 system the device type should be CTC, not BCTC.
  Note:  The BCTC MUST be attached to the CTC side of the
  chpid in order for this method to function.
  ****************************************************************
  MSGCBDA107I EC LEVEL xxxxxx INVALID may be issued. The EC level
  parameter is ONLY required if there exists more than one SUPPORT
  LEVEL for the same PROCESSOR type. HCD then uses this parameter
  to select the correct SUPPORT LEVEL for the PROCESSOR type. The
  EC LEVEL associated with the PROCESSOR SUPPORT LEVEL for HCD can
  be obtained by the LIST SUPPORTED PROCESSOR panel in HCD dialog.
  ****************************************************************
  A D/T3172-3 ( model 3) attached to an ESCON CHPID should be
  defined to HCD in the CONTROL UNIT and DEVICE panels as
  UNIT=SCTC . 3172  D/T3172
  If APAR OY67361 is applied, code the 3172 as a 3172.
  ****************************************************************
  If devices are DELETED, HCD will automatically delete them from
  the ESOTERIC LIST. So, to change already existing NON-ESCON
  devices to ESCON devices, you only have to DISCONNECT them from
  the CONTROL UNITS they are defined to. Then, you can change the
  CONTROL UNIT definitions and RECONNECT the devices to the
  changed CONTROL UNITS. Using this procedure, the ESOTERIC LIST
  will stay unchanged.
  ****************************************************************
  Abend00f 990106 0990106 106 could occur if a backleveled of
  HCD panels are being used, ie. R201 panels on a R301 system.
  Refer to installation informational apar II05254 for
  installation information.
  Abend will also result if incorrect CLIST is being used,
   ie. HCD R3 uses NEWAPPL(HCD) R5 will use NEWAPPL(CBD).
   In this case check to see if another CLIST may be
  concatenated ahead of SYS1.SCBDCLST.
  ***********************************************************
  WAIT078 IEC331I at IPL time.  DFP 3.2 does not support
  devices that are defined with DYNAMIC=YES.
  additional symptom:
  Message ikj58508i w/dair 6704 (msgIKJ58508I rc6704 dair6704)
  may be seen to indicate DFP3.2 cannot handle Dynamic UCBs.
  (dynamic activate)
  DEVSERV command does not show that the dynamic devices exist.
  ***********************************************************
  ABEND00F RC 0990406 990406 check to see if IODF is truncated
  abend has been since for CBDMRRET and CBDMRMIG.  The
  cause of truncation was not determined.
  ************************************************************
  ****************************************************************
  IEW0731 MSGIEW0731 after apply of UY91054 on CBDP0032 and
  CBDP0033.  This message is issued because HCD used the same
  alias and member name.  This message can be ignored and
  development has agreed to no longer use the same alias.
  ****************************************************************
  When MIGRATING an MVSCP deck in BATCH (with an invalid IODEVICE
  statement), error message MSGCBDG080I 'NO EDT DEFINED' is
  issued after the 'PARM='PRODIODF' STEP is executed. This
  message is validly issued. The first error (in the
  'PARM='MIGR' step) is shown in the '.MESSAGES' DATA SET as
  documented in the HCD USER's GUIDE on page 8.19 where the
  MIGRATION LOG is discussed.
  ****************************************************************
  When using the HCD Processor List panel to "overtype" a
  processor model the following msg may appear:
   CBDA105I This processor type-model is not supported by the
    specified support level.
  .
  Use the 'c' (change) option to change the processor model for
  this case.
  ****************************************************************
  IOS445I MSGIOS445I Physical Device is inconsistent with logical
  definition for a CISCO router.  Router was defined as a 3088
  definition was changed to RS6K to correct the problem.
  ****************************************************************
  For diagnosis of a WAIT0B1 , any reason code, see module
  IEAIPL43 . If messages are not issued on the CONSOLE, they
  will be in the MODULE's virtual storage. REG 12 will point to
  the beginning of the module.
  IEAIPL43 may also call IOSIOFR to read the IODF file. IOSIOFR
  can also issue the WAIT0B1 RC01 if it cannot find the IODF.
  One reason for a RC01 is if a customer appends a low-level
  qualifier to the IODF name (i.e. sys1.iodf00.data). To
  correct the situation use the IDCAMS ALTER facility.
  ****************************************************************
  IEV044 **Error** Undefined Symbol may be issued after migrating
  an HCPRIO deck using HCD if an END statement is included in
  the HCPRIO deck. This also can occur if there is an END
  statement in the input IOCP deck. MSGIEV044.
  ASMA044E may also be issued depending on which level of
  assembler is being used.
  ****************************************************************
  MSGIOS500I Reason=0167 167 0167 CCM could not enter
             configuration mode
             DESCTEXT = Dynamic I/O configuration capability
             disabled, POR required
  Check to see if the Allow Modification and Percent Expansion
  options are selected on the processor.
  1) On the 9021 these can be found on the CONFIG frame 2 of 2.
  2) On the 9221 these can be found in the profiles.
  .
  Note that the percent expansion may only be changed at POR time
  but the Allow modification may be selected before or after POR.
  ***************************************************************
  When Viewing a Control Unit using HCD the PROTOCL value can
  be viewed by using HRIGHT on panel CBDPCU32
  ***************************************************************
  When migrating an IOCP deck to HCD, HCD will not accept a
  CNTLUNIT statement with UNIT=CTC and PROTOCL of S or S4.  If
  the CTC or CTC-like control unit supports S or S4, then
  UNIT=3088 should be specified on the CNTLUNIT statement.
  ***************************************************************
  unpredicable results can occur if a PROGRAM invokes DYNAMIC
  ALLLOCATION and uses OLD macro's (i.e. IOSLOOK) instead of the
  UCBLOOK macro to obtain UCB data. This would ONLY occur if the
  devices were gen'd as DYNAMIC instead of STATIC via the HCD
  PANELS. Until the program can be changed, the STATIC parameter
  must be used.
  ****************************************************************
  CBDA563I 'Space exhausted in work IODF xxxx'  followed by
  CBDA099I 'Internal logic error detected in module CBDMS
  Reason code = 153, error info = 00000008 0000000F 20530000 PMVS
  
  ****************************************************************
  When using an OS Group change the generic and certain device
  features may change for the entire group of devices that is
  being changed, use this with discretion.
  ****************************************************************
  HCD UDT's CBDES000 - CBDES256 ) need to be instaled in
  SYS1.NUCLEUS
  ****************************************************************
  D/T3898 and D/T3897 should be gen'd using HCD as
  CNTLUNIT UNIT=3088 and IODEVICE UNIT=CTC
  ****************************************************************
  WAIT031 UCB for SYSRES device not found.  Using procedure in
  OW01978 make sure that:
  1) Correct Loadxx memeber is used.
  2) Correct IODF is used.
  3) Correct OS is used.
  4) Using the above IODF make sure that SYSRES device is
     connected to an OS.
  5) Check for MSG IEA521I UIM not found in MQE's, if this is
     the case install the correct UIM in SYS1.NUCLEUS.
  *********************************************************
  Informational message MSGCBDG084I will be issued if a
  DUMMY is coded for the CONTROL UNIT 'type' and the
  PROTOCOL is coded as 'D'.
  This is an informational message only. The UIM
  (CBDUS050) has been designed to allow for the highest
  possible protocol. The highest protocol that the
  CONTROL UNIT can handle should be coded.
  ******************************************************
  MSGCBDA107I CBDA107I EC-Level is not valid for 3090 600J
  when using EC-Level 227578 for a 3090 600J.
  In this case EC-Level 227574 should be coded.
  ********************************************************
  If migrating to HCD on a D/T4381 and using a D/T3205 as
  the NIP or MASTER CONSOLE and have UNIT = LCA coded in
  the CONTROL UNIT MACRO, HCD error message MSGCBDA234I
  UNKNOWN TYPE LCA will be issued. The resolution is to
  code UNIT = 3274 instead of LCA. There is no UIM that
  allows LCA and this is the reason HCD issues this message.
  **********************************************************
  When attempting to install HCD via CBIPO MSGCBDA046I
  CBDA046I may occur.  This msg may be ignored however since
  the COND statement of the EXEC in the CBIPO step contains
  COND=(0,NE) this will cause subsequent steps to be flushed.
  Change the cond parm so that the CBIPO init step will run
  even if a RC=4 is received.
  Also INIT step of the CBIPO job may fail due to a cond of 4 and
  IEC161 72-053.  Since this step failed the .cluster data set for
  te PROD step was never created, thus the production step failed
  Wth CBDA469I RC8 RSN28.  Change the cond on the INIT stop and
  Change the cond on the INIT step and re-run the PROD step.
  .
  ***************************************************************
  When defining an OEM DASD device ( ie. ICEBERG ) as a 3990
  if a model is used on the control unit
   CBDA299I MSGCBDA299I Control unit xxx has more than max number
   of devices attached
  is rec'd.  In this case the model parameter should not be used.
  If the model parameter is not used the UIM allows up to 256
  devices to be attached.
  MSGCBDA299I may also be issued when defining
  256 devices for 9393 X83 if the model is specified
  on the CNTLUNIT definition TYPE= parameter.
  Removing the model from the CNTLUNIT definition
  resolves the problem.
  
  ***********************************************************
  ISPP100 panel CBDCxxx not found when accessing HCD help
  panels.  ie, CBDC099 when using HCD R501 under MVS 4.3
  Problem here is that user has an old R301 clist
  concatenated ahead of SYS1.SCBDCLST.
  ***********************************************************
  MSGCBDA125I issued when using the TRACE command in the
  HCD PROFILE dataset and this dataset is 'sequenced'.
  The 'sequence' number is shown in this error message.
  To resolve this problem, set NUMBER OFF from ISPF when
  editing this dataset.
  ************************************************************
  CBDA153I  MSGCBDA153I Channel path ID 00 already exists.
   when chpid 00 id not in the migration input deck.
  Check to see that the correct MACLIB is being used.
  *************************************************************
  WAIT0B1 RC 006 6 when IPL'ing from an IODF generated after
  running the CBIPO dialogs and using the copy function.
  Ensure that the OS and EDT in the LOADxx member correspond
  to the OS and EDT in the IODF that was used as the source
  of the copy.  If the LOADxx member contains CBIPO as the
  OS and the source of the copy contains a different OS id
  this would cause a WAIT0B1 RC 0006
  *************************************************************
  
  MSGCBDA268I CBDA268I No Control Unit Information Table found
  for DEV# issued during CBIPO install or when running HCD dialog
  or batch.  This message is issued when HCD cannot find the
  UIM(s) in SYS1.NUCLEUS.  If the user has the UIM(s) in a
  library other than SYS1.NUCLEUS a HCDPROF DD statement is
  required with UIM_LIBNAME=library that contains UIMs and
  UIM_VOLSER=volser of library.  See HCD Users Guide (SC33-6468)
  chapters 2 & 12 for more information.
  **************************************************************
  If you are using HCD on a system with a DFP level that is
  higher than the one being IPL'd the following msg's may be
  surfaced to the user at IPL time or when using HCD:
  MSGCBDA381I PARAMETER 33 or 34 FOR DEVICE xxx NOT FOUND IN UDT
              CBDES005 .
  This msg is issued during IPL of MVS or using HCD due MISMATCH
  in PTF levels of module CBDES005. If 'TAPE LIBRARY SUPPORT' or
  'AUTOSWITCH (D/T3495) is not used, these msgs can be ignored.
  To eliminate the message for parameter 33, CBDES005 must be at
  ptf level UW01274 for DFP 3.3 (APAR is OW00644).
   To eliminate the message for parameter 34 CBDES005 must
  be at ptf level UW20584 for DFP 3.3 (APAR is OW14622).
  ************************************************************
  MSGCBDG300I - Insufficient authority to process the request.
  On the HCD ADD PROCESSOR panel if you do not have RACF or
  another security package installed, you must leave the
  'Network name' and 'CPC name' fields blank. If they are
  not blank you will receive MSCBDG300I and the job will
  cancel when you run the iocp job to create the IOCDS.
  CBDG300I
  ********************************************************
  MSGCBDA560I CBDA560I - If the HCD migration log and the
  .LISTING file do not have any information as to which
  statement is in error check the level of module CBDZPARS in
  SYS1.MACLIB. The customer may be running with an HCSH301
  version. If running HCD V5.1, the module should be at
  HCSH501.
  ***********************************************************
  HCD AND COUPLING FACILITY ( CF ) PARTITION 9672
  ICMF MSGCBDG401I and 9121 511-based
  *
  HCD will not allow a CF partition to be defined on these
  processors, only allows OS type partitions.  CF channels are
  not supported by hardware.. But ICMF can be run in a
  partition, simulating coupling facility functions.
  .
  If you attempt to define a 'CF' partition on the 'ADD PARTITION'
  panel in HCD, you will receive the following message:
  'CBDG401I Usage type CF specified for partition XXX is not
   supported by processor'
  *
  There is no reason to define a partition as CF in HCD if
  CF channels are not supported on the hardware.
  ICMF can be run in an OS partition which is defined in HCD.
  At POR the partition is defined as a CF to the hardware.
  You may get a warning message when you do this:
  CBDA857I NO CHANNEL PATHS ATTACHED TO PARTITION.
  This message may be ignored.
  On the processor, you must turn on ICMF for the partition.
  Choose CF then ICMF.
  ****************************************************************
  When attemping to migrate extended user parmameter's ( USERPRM )
  on the IODEVICE macro use only the UIM Private Parameter's as
  documented in the HCD User's Guide.  DYNAMIC and LOCANY are
  NOT private parameter's.  If DYNAMIC and LOCANY are to be set
  specify:
    IODEVICE UNIT=3380,ADDRESS=(520,32),CUNUMBR=(050,150),
         FEATURE=(SHARED,ALTCTRL),DYNAMIC=YES,LOCANY=YES
  KEYWORDS:
   MSGCBDA857I MSCBDA857I 9672 MSCBDG401I
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• cancelled as info apar.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels