II09372: INFORMATION APAR FOR DFSORT/VSE (5746SM310) FOR RELEASES V3R1, V3R2, AND V3R3.

APAR status

• Closed as canceled.

Error description

• THIS INFO APAR IS FOR DFSORT/VSE (5746SM310) R310 AND R320 AND
  WILL CONTAIN INFORMATION THAT HAS NOT BEEN APAR'D UNDER NORMAL
  PROCEDURES.
  PLEASE USE THE FORMAT BELOW FOR DOCUMENTING SUGGESTIONS, TIPS,
  HINTS, AND OTHER SPECIFIC INFORMATION TO BE INCLUDED.
                                                                 .
  EXAMPLE:
  1 - (MM/DD/YY)
  DESCRIPTION: A brief one sentence description.
  DETAILS: A detailed description of the problem, suggestion,
           or other information.
  KEYWORDS: Keywords or variations of words used in describing
            info.(ie. INFO APAR INFOAPAR STORAGE MSGxxxx  etc.)
  =============================================================
  1 - (04/03/96)
  DESCRIPTION: Info on PSP Buckets for Sort/Merge 2.5 and
               DFSORT/VSE 3.1 and 3.2.
  DETAILS: You can find the subsets for the sort products in
  the following VSEESAxxx PSP buckets.
   UPGRADE    SUBSET       PRODUCT/REL.
   ---------  --------     ------------
   VSEESA113  SORTMRG/F46  SORT/MERGE 2.5
   VSEESA211  SORT/31A     DFSORT/VSE 3.1
   VSEESA212  SORT/32A     DFSORT/VSE 3.2
  Although we recommend that you run the sort product that is
  documented in the PSP Bucket for that level of operating
  system, you can run a lower level of sort. If you need the
  PSP Bucket for your sort product for information on HIPER
  apar's and such you will need to get the PSP Bucket that
  contains the sort SUBSET that you are currently running.
  For Example... If you have installed VSE/ESA 2.1.2 but are
  running DFSORT/VSE 3.1 then you will need to get the PSP
  Bucket for VSEESA211 for the SORT/31A SUBSET (containing
  all the necessary HIPER apars for DFSOR/VSE 3.1 and other
  pertinent information related to that release).
  The PSP Bucket for VSEESA212 will only contain the SUBSET
  for the DFSORT/VSE 3.2 (SORT/32A) product.
  KEYWORDS: PSP BUCKET SORT/32A SORT/31A SORTMRG/F46 UPGRADE
  .
  2 - (04/03/96)
  DESCRIPTION: DFSORT/VSE Web Page.
  DETAILS: To keep current on the latest information regarding
           DFSORT/VSE, visit our WWW page at the below URL:
           http://www.storage.ibm.com/storage/software/
                  /sort/srtvhome.htm
  KEYWORDS: WORLD WIDE WEB DFSORT VSE URL
  .
  3 - (08/06/96)
  DESCRIPTION: When executing the DFSORT/VSE verification job
   ILUSDATA receives an MSG0S03I PGM CHECK INTERUPTION. OPERA-
   TION EXCEPTION ERROR.
  DETAILS: Diagnosis of the problem shows that the error was
   occuring on a branch to a DFSORT/VSE module but instead of
   getting the first executable instruction the branch was
   landing on the eyecatcher information. It was determined
   that the problem is in the way sample application ILUSDATA
   invokes merge. DFSORT/VSE runs OK, created three sample
   files and these files can be used. The application could not
   print "good-bye" message. This problem 'appearance' depends
   on how SYSLST is allocated in VSE/ESA. To avoid this problem
   the customer can change the last assembler statement before
   the END as:
     LOAD   DS   8000D   DFSORT/VSE LOAD POINT
   This should correct the problem for the time being. The dev-
   opment team has indicated that this will be fixed in the
   future.
  KEYWORDS: ILUSDATA 0S03I ABEND0C1 SYSLST BRANCH
  .
  4 - (11/18/96)
  DESCRIPTION: END statement - V3R2 vs V3R1.
  DETAILS: It has been found that DFSORT/VSE V3R2 implements the
  END control statement differently then DFSORT/VSE V3R1 and
  DOS/VS VM/System Product Sort/Merge V2R5. We investigated and
  found that V3R2 did indeed implement the END control statement
  in a different way then DFSORT/VSE V3R1.
  Here is an explanation of the differneces:
  - SM2 and V3R1
    The END statement tells DFSORT/VSE to stop reading input and
    give 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 the end-of-data when END was specified
                                                               .
  - V3R2
    The END control statement allows V3R2 to stop accepting
    control statements. Any statements (for example, control
    statments, // statements, ect.) 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 books because the
    complaints were our first indication that this problem
    existed.
  .
  We have written a ZAP that will allow V3R2 to process the END
  control statement like V3R1 and SM2 did. Hopefully, the ZAP
  will give you some breathing space so you can insert the /*
  statments. If you are interested in receiving this ZAP, please
  contact the IBM Support Center and ask for Level 2.
  .
  5 - (3/27/97)
  DESCRIPTION: ILUINST options not changing.
  DETAILS: When changing the default options using ILUINST, an
   assemble and relinked were performed but the changed options
   did not take effect.
   If sort was installed in the SVA, then a SET SDL or an IPL
   must be done to take effect.
  KEYWORDS: ILUINST SVA ASSEMBLE RELINK
  .
  6 - (8/25/97)
  DETAILS: When using SUM FIELDS=NONE and EQUALS the
   DFSORT/VSE Application Programming Guide for Rel 3.1 and
   3.2 states "EQUALS is ignored when the SUM statement is
   specified".  This is working incorrectly and EQUALS is not
   ignored as it should be and stated.
   This has been corrected in the current DFSORT/VSE Rel 3.3.
  KEYWORDS: SUM FIELDS NONE EQUALS INCORROUT
  

Local fix

• ADDITIONAL KEYWORDS:
   5746SM310 INFOAPAR INFO APAR
  

Problem summary

Problem conclusion

Temporary fix

Comments

• this is a 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