II11639: DOC ERRORS SDF II ADMINISTRATOR'S GUIDE REL 4 SH19-8211-00

APAR status

• INTRAN

Error description

• SH19-8211-00 SH19821100 5665-366 5665366 140
  Documentation errors in SDF II ADMINISTRATOR'S GUIDE RELEASE 4
  

Local fix

• Chapter 2. Adapting the SDF II installation
  under heading General Definitions on page 6
  Correct outline of panel DGIIE800:
  - Remove Line 2 (DGIIXINV options......)
  - Change line Old DGIIXINV   PRIVATE.CLIST(DGIIXINV) to
    Old DGIIXINV   *RIVATE.CLIST(DGIIXINV)
  - Remove line starting with 'Private Table Output....'
  - Adjust index numbers alongside panel DGIIE800
    e.g. 9 refers now to Private Skeleton Library,
        10 to Private  Load Library etc.
  
  Change the description of panel DGIIE800 on page 6
  point 2 and from point 8 onwards to the following:
  2.The name of an existing DGIIXINV that will be used to copy
    the previous customization info into the new procedure.
    Note:
    a. The old DGIIXINV must have been created by the DGIIXIN1
       procedure.
    b. After the info is copied, the first letter of the name
       is commented out by an *. This is an indicator, that
       the information is already copied. If the * is removed,
       the information will be copied again.
  
  8. Private table library.  If specified here it will be
     allocated as private table output library and as private
     table library before the SDF II table library.
     If not specified, either the ISPF profile dataset or (if
     the profile dataset name is omitted in the customization
     panel) ISPF.ISPPRlangcode will be used.
  9. Private skeleton library.  If specified here it will be
  allocated before the SDF II skeleton library.
  10.Private load library.  If specified here it will be
    allocated before the SDF II load library.
  11.SDF II print and trace output definition.
  12.SDF II DBCS Print output definition.
  13.SDF II DBCS Print outlined output definition.
  -------------------------------------------------------------
  Page 9 under heading 'Define Prototype Libraries'
  
  1. Define the DDname and data set name for the prototype
     datasets. They should reflect the datasets used during
     prototyping for define and run a prototype.
  
  2. Define the dataset name for the prototyping panel input
     library. This name should reflect the dataset used during
     prototype panel generation and will contain the ISPF
     prototype panels.
  Note: If prototyping is going to be used during the invocation
        of SDF II, neither the prototype libraries nor the
        prototype panel input library can be omitted.
  
  Page 10 under heading 'Generated Output Datasets'
  
  1. Define DDname and data set name for generated output
     datasets. These datasets have to be specified, if a DDNAME
     instead of the full dataset name is going to be used during
     panel generation.
  Page 11 under heading 'Optional Definitions and Allocations'
  
  7. Specify the name of the ISPF profile data set.
     If this dataset does not exist, it will be created for
     BATCH invocations ONLY if YES is specified at
     'Need ISPF-Allocation ?'
  ----------------------------------------------------------------
  Chapter 4. Interfacing with SDF II, page 53,
             Figure 20. Variables for generation parameters for
                        CICS/BMS (Panel DGICE10)
  Add option 'length statement    COBOL language only' as follows:
  
  ICV10DAL Alignment              Ignored for C language
  ICV10DGR Graphic                DBCS panels only
  ICV10DTR Trigraph               C language only
  ICV10ADI SDF/CICS Compatible    COBOL language only
  ICV10CLG Length statement       COBOL language only
  ICV10DEF Field names            Field names generated as defined
  
  Note: ICV10DEF is used in the generation of CICS/BMS source
        statements to use the full SDF II field name as the label
        of the DFHMDF statement.
  
  ----------------------------------------------------------------
  Chapter 6. Importing objects into SDF II
  
  Add new subheading:
  Recovering lost SDF II panel object
  
  Should an SDF II panel object be deleted, it should able to be
  recovered if the SDF II generated CICS/BMS source and data
  structure is available.  A rexx exec (DGIDSBMS) is provided
  in the installation ...SDGICMD data set.  DGIDSBMS parses both
  the SDF II generated CICS/BMS source and data structure to
  output a member containing "*DGI" statements preceding the
  CICS/BMS source.  This output can then be imported using the
  SDF II import utility (specify CICS/BMS as the input source
  type).
  
  ----------------------------------------------------------------
  Chapter 7. Migrating from one SDF II release to the next
             Migrating to Release 4
  Add new subheading:
  
  Change of object representation
  
  Each object is stored as a sequence of 80 byte records. Pre
  Release 4, the first 72 bytes of each record contained the
  data of the object, the remaining 8 bytes contained a sequence
  number. From Release 4 onwards the whole 80 byte record is
  used to store the data of the object.
  
  SDF II 1.4 will automatically change 72 byte data records from
  earlier releases to 80 byte data records when the object is
  first edited and saved within SDF II 1.4.
  
  This results in forward, but not backward compatibility of the
  SDF II objects. While pre release 4 objects can be edited in
  release 4, trying to edit a release 4 object in release 3
  will lead to Message DGILM004 (Object destroyed).
  

Problem summary

Problem conclusion

Temporary fix

Comments

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