IBM Support

II09684: DFSORT/VSE END CONTROL STATEMENT IMPLEMENTATION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • We have received comments that DFSORT/VSE V3R2 implemented the
    END control statement differently than DFSORT/VSE V3R1 and
    DOS/VS VM/System Product Sort/Merge V2R5 (SM2).  We have
    investigated, and found that V3R2 and later versions did
    indeed implement the END control statement in a different way.
    Here is an explanation of the differences:
    SORT/MERGE V2R5 and DFSORT/VSE V3R1:
    
    The END statement tells DFSORT/VSE to stop reading input and
    control back to the system.  All statements following the END
    are read by the system.
    
    Thus, SM2 and V3R1 erroneously ignored the system requirement of
    using /* as end-of-data when END was specified.
    .
    DFSORT/VSE V3R2 AND LATER VERSIONS (3.3 AND 3.4)
    The END control statement allows V3R2 to stop accepting control
    statements.  Any statements (for example, control statements,
    // statements, etc.) between the END and /* are read by
    DFSORT/VSE, but not processed.
    
    Thus, V3R2 now follows the system requirement of using /* as
    end-of-data.  Unfortunately, this means that customers who do
    not specify /* after END will have statements ignored by V3R2
    that were previously processed by the system.  This situation
    is not documented in our manuals because we were unaware that
    this presented problems to our customers.
    
    We are very sorry if you have encountered this problem, and
    it has caused you any inconvenience. We have written ZAPs that
    allow V3R2 and later versions to process the END statement as
    it did in SM2 and V3R1. Hopefully, these ZAPs will give you
    the time you need to add the /* statements at a pace that is
    appropriate for your environment. Listed below are the ZAPs
    for the supported releases. If you have any problems with these
    please contact the IBM support center.
    
    The ZAPs are listed below for each DFSORT/VSE release:
    DFSORT/VSE 3.2
     // JOB JOBZAP
     // OPTION NODECK,NOXREF,JCANCEL,CATAL
     // EXEC MSHP
     PATCH S=SORT.KV3R2PTF
     AFFECTS PHASE=ILUSDEF1
     ALTER 3056 45A0B7DA : 47000000
     ALTER 3056 47F0C1B8 : 47000000
     /*
     /&
    .
    DFSORT/VSE 3.3
     // JOB V3R3ZAP
     // OPTION NODECK,NOXREF,JCANCEL,CATAL
     // EXEC MSHP
     PATCH S=PRD2.PROD
     AFFECTS PHASE=ILUSDEF1
     ALTER 2FA4 45A0B9A0 : 47000000
     ALTER 2FA8 47F0C042 : 47000000
     /*
     /&
    .
    DFSORT/VSE 3.4
     // JOB V3R4
     // OPTION NODECK,NOXREF,JCANCEL,CATAL
     // EXEC MSHP
     PATCH S=PRD2.NIKLIB4
     AFFECTS PHASE=ILUSDEF1
     ALTER 2ED8 45A0B752 : 47000000
     ALTER 2EDC 47F0C042 : 47000000
     /*
     /&
    .
    ADDITIONAL SYMPTOMS:
    5746SM310 R31A R32A R33A R34A INFOAPAR INFO APAR END
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • Closing information for APAR II09684
    

APAR Information

  • APAR number

    II09684

  • Reported component name

    PA LIB INFO ITE

  • Reported component ID

    INFOPALIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1996-09-06

  • Closed date

    1996-09-06

  • Last modified date

    1998-10-27

  • 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

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG32M","label":"APARs - VSE\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"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":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
27 October 1998