IBM Support

OA41515: PIPE EDIT HDRMTYPE ORDER MISSING DOCUMENTATION IN THE NETVIEW FOR Z/OS 6.1 PUBLICATION PROGRAMMING: PIPES

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible in next release.

Error description

  • PIPE EDIT HDRMTYPE order missing documentation
    HDRMTYPE (input order)
    Indicates that the one-byte message type indicator is to be
    read in the message line that is being processed.
    HDRMTYPE (output order)
    Indicates that the one-byte message type indicator is to be
    written in the message line that is being processed.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of Tivoli NetView for z/OS.        *
    ****************************************************************
    * PROBLEM DESCRIPTION: There are many errors in the            *
    *                      description of PIPE EDIT.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Many inconsistencies, omissions, and extraneous information is
    in the description of the EDIT pipe stage. See the Comments
    section for details.
    

Problem conclusion

Temporary fix

Comments

  • The description of the EDIT stage in the Tivoli NetView for z/OS
    V6R1 Programming: Pipes manual (SC27-2859-02) should be changed
    as follows:
     - Changes to the Global Order syntax diagram:
       - "FINDLINE string" should be changed to "FINDLINE /string/".
       - "NEXTLINE" should be added
       - "SETBEEP" should be added
     - Changes to the Input Order syntax diagram:
       - "DELETE" should be added
       - "FLGDSCD-n" should be added
       - "FLGRTCD-n" should be added
       - "HDRMTYPE" should be added
       - "IFRAUIN3" should be added
       - "MSGSENDR" should be added
     - Changes to the Conversion Order syntax diagram:
       - "D2X" should be added
       - "JOBNAME" should be added
     - Changes to the Output Order syntax diagram:
       - "ACTIONDL" should be removed
       - "AutoInt" should be removed
       - "DELETE" should be added
       - "FLGDSCD-n" should be added
       - "FLGRTCD-n" should be added
       - "HDRMTYPE" should be added
       - "REPLYID" should be removed
     - Changes to the Synonum table:
       - An entry should be added that has MSGSENDR as the Stage
         Operand and MSGSENDER as the Synonym
     - Changes to the Global Order Summary table:
       - The "FINDLINE" global order should be changed to "FINDLINE
         /string/"
       - The "LOGTO" global order should be added, with the
         following text as the Task Performed:
             Sets an option to log messages that are displayed
             using the CONSOLE stage or ROUTE stage.
       - The "NEXTLINE" global order should be added, with the
         following text as the Task Performed:
             Specifies both the READLINE and WRITELINE keywords,
             and advances both the input message line (source)
             and the output message line (destination).
       - The "NOLOGTO" global order should be added, with the
         following text as the Task Performed:
             Sets an option to not log messages that are
             displayed using the CONSOLE stage or ROUTE stage.
     - Changes to the Input Order Summary table:
       - The "DELETE" input order should be added, with the
         following text as the Task Performed:
             Determines whether a message has been previously
             deleted.
       - The "FLGDSCDn" input order should be added, with the
         following text as the Task Performed:
             Indicates that the specified descriptor code byte
             is to be read.
       - The "FLGRTCDn" input order should be added, with the
         following text as the Task Performed:
             Indicates that the specified route code byte is to
             be read.
       - The "HDRMTYPE" input order should be added, with the
         following text as the Task Performed:
             Indicates that the one-byte message type indicator
             is to be read.
     - Changes to the Conversion Order Summary table:
       - The "D2X" global order should be added, with the following
         text as the Task Performed:
             Converts a decimal number to hexadecimal
             representation.
     - Changes to the Output Order Summary table:
       - The "DELETE" output order should be added, with the
         following text as the Task Performed:
             Deletes a message or command, or undeletes a
             previously deleted message or command.
       - The "FLGDSCDn" output order should be added, with the
         following text as the Task Performed:
             Indicates that the specified descriptor code byte
             is to be written.
       - The "FLGRTCDn" output order should be added, with the
         following text as the Task Performed:
             Indicates that the specified route code byte is to
             be written.
       - The "HDRMTYPE" output order should be added, with the
         following text as the Task Performed:
             Indicates that the one-byte message type indicator
             is to be written.
       - The "MRT" output order should be added, with the following
         text as the Task Performed:
             Indicates that the message has been exposed to the
             Message Revision Table.
     - Changes to the Supported environments table:
       - "C2GV" should be added, applicable to the following
         environments:
         - PIPE
         - Auto Edit and Acquire
         - CBE
       - "COPYREVERSE" should be changed to "COPYREV"
       - The entry for CURRLINE should be removed
       - "flag_bytes" should be added, applicable to the MRT REVISE
         and WHEN environment
       - "LOGTO" should be added, applicable to the PIPE environment
       - "NOLOGTO" should be added, applicable to the PIPE
         environment
       - "NOTECHO" should be added, applicable to the PIPE
         environment
       - "position" should be added, applicable to all environments
       - "READSCRATCH" should be removed
       - "REPLYID" should be removed
       - "READSRC" should be added, applicable to the CBE
         environment
       - "REVERSECOPY" should be removed
       - "SCRATCH" should be removed
       - "WRITESCRATCH" should be removed
     - Changes to descriptions of Global Orders:
       - The first description of NOTECHO should be removed
       - The description of SETBEEP should be added, which reads as
         follows:
           SETBEEP (global order)
             Sets an audible alarm for message output. When the
             message output is displayed, the audible alarm is
             issued.
     - Changes to descriptions of Input Orders:
       - The description of DELETE should be added, which reads as
         follows:
           DELETE (input order)
             Determines whether a message has been previously marked
             for deletion. If the message has been marked for
             deletion, the DELETE input order supplies a non-null
             output; if the message has not been marked for
             deletion, the output is a null character. This output
             can be used as input to other decision-making orders
             such as the YESNO order.
    
             The DELETE input order is only available for message
             revision.
       - The description of FLGDSCDn should be added, which reads as
         follows:
           FLGDSCDn (input order)
             Indicates that the specified descriptor code byte is to
             be read, where n is 1, 2, 3, or 4. The value of the
             byte is supplied as a string of eight EBCDIC values
             (either 0 or 1).
       - The description of FLGRTCDn should be added, which reads as
         follows:
           FLGRTCDn (input order)
             Indicates that the specified descriptor code byte is to
             be read, where n is 1 to 16. The value of the byte is
             supplied as a string of eight EBCDIC values (either 0
             or 1).
       - The description of HDRMTYPE should be added, which reads as
         follows:
           HDRMTYPE (input order)
             Indicates that the one-byte message type indicator is
             to be read in the message line that is being processed.
       - The description of IFRAUIN3 should be added, which reads as
         follows:
           IFRAUIN3 (input order)
             Indicates that the 32 bits that are defined as IFRAUIN3
             are used as input. For these 32 flags, see the DSIIFR
             assembler macro.
       - The following msgattr values should be added:
         - IFRAUIN3, which reads as follows:
             IFRAUIN3
               Indicates that the 32 bits that are defined as
               IFRAUIN3 are used as input. For these 32 flags, see
               the DSIIFR assembler macro.
         - MSGSENDR, which reads as follows:
             MSGSENDR
               Indicates that the edit phrase input is the
               8-character name (OPID) of the task that created the
               message or, if the message was routed between tasks,
               that most recently sent the message.
       - The description of MSGSENDR should be added, which reads as
         follows:
           MSGSENDR (input order)
             Indicates that the edit phrase input is the 8-character
             name (OPID) of the task that created the message or, if
             the message was routed between tasks, that most
             recently sent the message.
       - The descriptions of the following input orders should be
         unindented, to line up with the other input orders:
         - NVABLE
         - ROUTECODES
         - SESSID
         - SYSCONID
         - SYSNAME
     - Changes to descriptions of Conversion Orders:
       - The description of D2X should be added, which reads as
         follows:
           D2X (conversion order)
             Specifies that a decimal number is to be converted to
             hexadecimal representation.
     - Changes to descriptions of Output Orders:
       - The description of CHKEY should be removed
       - The description of DELETE should be added, which reads as
         follows:
           DELETE (output order)
             Deletes a message or command, or undeletes a previously
             deleted message or command, depending on the input:
    
             *  If the input is null, the letter N, or the number 0,
                the DELETE output order undoes a previous deletion.
    
             *  If the input is a non-null value other than the
                letter N or the number 0, the DELETE output order
                deletes the message or command.
    
             The DELETE output order is available only when
             performing a REVISE action.
       - The description of FLGDSCDn should be added, which reads as
         follows:
           FLGDSCDn (output order)
             Indicates that the specified descriptor code byte is to
             be written, where n is 1, 2, 3, or 4. The value of the
             byte is changed according to the input mask. The input
             mask must be a string of eight EBCDIC values (0, 1, or
             x). Each descriptor code flag bit that corresponds to a
             0 is turned off; each descriptor code flag bit that
             corresponds to a 1 is turned on; and the other bits are
             left as is.
       - The description of FLGRTCDn should be added, which reads as
         follows:
           FLGRTCDn (output order)
             Indicates that the specified route code byte is to be
             written, where n is 1 to 16. The value of the byte is
             changed according to the input mask. The input mask
             must be a string of eight EBCDIC values (0, 1, or x).
             Each route code flag bit that corresponds to a 0 is
             turned off; each route code flag bit that corresponds
             to a 1 is turned on; and the other bits are left as is.
       - The description of HDRMTYPE should be added, which reads as
         follows:
           HDRMTYPE (output order)
             Indicates that the one-byte message type indicator is
             to be written in the message line that is being
             processed.
    The online help for PIPE EDIT is being changed to reflect the
    above.
    

APAR Information

  • APAR number

    OA41515

  • Reported component name

    NETVIEW FOR Z/O

  • Reported component ID

    5697NV600

  • Reported release

    10B

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-20

  • Closed date

    2013-06-06

  • Last modified date

    2013-08-02

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

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

    UA69413 UA69414

Modules/Macros

  • EUYPIEXE
    

Publications Referenced
SC27285902    

Fix information

  • Fixed component name

    NETVIEW FOR Z/O

  • Fixed component ID

    5697NV600

Applicable component levels

  • R10E PSY UA69413

       UP13/07/10 P F307

  • R10J PSY UA69414

       UP13/07/10 P F307

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJDU","label":"IBM Z NetView"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10B","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10B","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 August 2013