II08841: DFSORT REL 12.0 & 13.0 - OEM BUGS, COMMON USER ERR, UMOD INFO, PERFORMANCE AND TUNING SUGGESTIONS, DOC ERRORS. (CON'T II09889)

APAR status

• Closed as canceled.

Error description

• 5740SM105, HSM1D00, VER 1 REL 12 MOD 0. ( D00 )
  5740SM105, HSM1F00, VER 1 REL 13 MOD 0. ( F00 )
  .
  Visit DFSORT/MVS on the WWW
  http://www.storage.ibm.com/storage/software/sort/srtmhome.htm
  .
  PROBLEM LIST. (Number entry item and place entry date on first
                 line of the information entry).
  .
  1- (7/27/95)
  *******************************************************
    THE STOPX37 USERMOD CODE HAS BEEN ADOPTED BY DFSORT
    DEVELOPMENT AS A PERMANENT FIX.  PLEASE APPLY THE
    FIX FOR APAR PN71337, UN90139 TO AVOID U1095 ABENDS.
    (NOTE: UN90139 IS PE'ED AND REQUIRES FIX FOR PN84250).
    NOW THAT A PERMANENT FIX IS AVAILABLE THE USERMOD FOR
    DFSORT R13, THE USERMOD WILL NO LONGER BE MAINTAINED.
  **********************************************************
  
   ABENDU1095 U1095 VIA A MSGICE185I RUNNING STOPX37 AND DFSORT
   The problem is encountered some OEM products such as STOPX37
  and SRS which dynamicly extends the SORTOUT data set. During
  the extend the TIOT offsets for this data set is relocated.
  DFSORT is unaware of the relocation of the TIOT entry.
  Additionally, the problem only occurs if the user is request-
  ing that diagnostic type of messages is issued via the
  //SORTDIAG DD DUMMY statement. The user that is experiencing
  these type of errors can request usermod 'INSTOPX' from the
  DFSORT Technical Office (DFSORT at SJSVM28) or from the
  Level 2/3 support group.
  .
  2- (7/2795)
   MSGICE141A SPANNED RECORD ON SORTIN COULD NOT BE ASSEMBLED.
  The cause of the ICE141A is that DFSORT detected an VBS input
  record that did not contain all the segments for that record.
  We usually see this when a customer has MAN-X and MAN-Y type
  records going into a temporay DASD buffer which holds them
  until they are MOD'd onto a Weekly/Daily data set either on
  a Tape or DASD. At some point in th past this buffer filled
  up and received a B37 type of abend. At this point, we had not
  finished writing the record and ended up missing a segment.
  This record is MOD'd onto an exsisting data set but now as
  the buffer starts to fill again we start with a new and
  complete record and have lost the missing segment. When this
  is eventually MOD'd onto the data set it is MOD'd onto the
  back end of the previous record (missing the segment). When
  DFSORT eventually uses this input file we check the SDW (Seg-
  ment Descripter Word) for each VBS record that is read in to
  see that all segments of the record are present. If not, we
  issue the ICE141A message and terminate the job. This has to
  be done in that if we processed the records we could have
  corrupted data for the output.
  To correct this condition, the user needs to insure that the
  temporary buffer that stored the records before migrating them
  to tape or DASD does not ever get into the situation that can
  result in a B37 type of error, such as dumping the records
  when it is 85% full. As to fixing the data set with the missing
  segments the customer needs to write a program that will read
  in the VBS records and check the SDW to see that it is valid
  and contains all segments. If a record is complete and OK then
  it gets put into a 'Good' data set to be sorted later. If it
  detects a record that is missing a segment then it is put into
  a 'Bad' data set and is converted to a VB record. The Level 2
  software support center has a SAMPLE assembler program that
  a customer wrote and fixes the bad data set. He supplied this
  to us for other customers that may have this problem.
  ** THIS PROGRAM IS IN NO WAY SUPPORTED BY IBM OR DFSORT **
  and is only to be used as an example for you to use. If you
  would like a copy of the assemble source code you can contact
  the DFSORT Level 2/3 and request 'ICE141A.FIXASM.A'.
  .
  3) (8/10/95)
    MSGICE129I INDICATES RESDNT=NONE EVEN THOUGH DFSORT IS
    INSTALLED RESIDENT (IN LPA).
  This is documented in the PSP bucket for Rel 13, HSM1F00,
  in Section #3, General Information. This will be corrected
  in future SPE APAR PN71337. There is no effect to the
  operation or performance of the product. This is only due to
  most modules being loaded above 16M line and a high order
  byte had not been cleared to indicate which text, 'ALL' or
  'NONE' to be inserted into the message text.
  .
  4 - (9/15/95)
    MSGISPV009 INVALID VARIABLE ".G..." ON INVOKED DFSORT FROM
    ISPF PANELS.
  The message ISPV009 will be issued if you have previously
  installed both the ENGLISH and JAPANESE panels for DFSORT.
  You should only have selected one or the other and not both.
  for Rel 12.0 the FMIDS are:
   ISPF BASE  - JSM1DJ0  (mandatory for ISPF)
    ENGLISH   - JSM1D01   < choose one
    JAPANESE  - JSM1D11   <or the other
  for Rel 13.0 (pre-UQ00530) the FMIDS are:
   ISPF BASE  - JSM1FJ0  (mandatory for ISPF)
    ENGLISH   - JSM1F01   < choose one
    JAPANESE  - JSM1F11   < or the other
  .  ** after UQ00530 you can select English, Japanese, or both.
  5- (9/22/95)
   MSGIEV042I and/or MSGGIM24001E RC=08 ISSUED WHEN ATTEMPTING
   TO CHANGE ICEMAC DEFAULT VALUES.
  When attempting to change the ICEMAC macro default values in
  the ICEAMx modules the customer may receive IEF042I 'PREVIOUSLY
  DEFINED SYMBOL DATA' and/or a GIM24001E RC08 ASSEMBLY ERROR
  FOR SYSMOD... due to the fact that they are not using the
  correct sequence numbers in the MSMOPT1 macro doing the assem-
  bly. The sequence numbers should start with 00550000 such as:
  ++ USERMOD(MSMOPT1) .
  ++ VER  (Z038) FMID (HSM1F00)  .
  ++ SRCUPD (ICEAM1)  DISTMOD (ICELIB) DISTLIB (AICESRCE) .
  ./ CHANGE NAME=ICEAM1
     ICEMAC      JCL,                                 X00550000
                 |                                    |
                16                                   72
  Some customers had copied the macro for use from prior releases
  (11 or 11.1) where the sequences numbers were different. The
  sequence numbers for ICEMAC INV, TSO, and TSOINV also need to
  start with 00550000. For a copy of the macro they can look in
  the Rel 12.0 SAMPLIB or the Rel 13.0 AICESAMP library for
  members SMOPRECE (12) or ICEOPREC (13).
  .
  6- (9/22/95)
   MSGGIM69102E, MSGGIM54601E, MSGGIM69149E and MSGGIM37001S
   MAY BE ISSUED RELATED TO DDDEF SCEELKED ON APPLY CHECK FOR
   DFSORT REL 13.0.
  SCEELKED is a DDDEF defined in sample job ICEDDEF for Rel 13.0
  for use when installing FMID JSM1FN0 for LOCALE PROCESSING
  (National Language Reference). If you selected that FMID during
  the APPLY check but did not previously define SCEELKED you will
  get allocation and SMP/E messages for no DDDEF entry. If you
  do decided to define SCEELKED the allocation for SYS1.SCEELKED
  would have been done when the required products LE/370 1.4
  -OR- MVS/ESA System Produc verion 5.2 with C Language Support
  Feature (5831/5832) were installed prior to the installation
  of DFSORT R13.0.  Please see the DFSORT PSP Bucket, Subset
  JSM1FN0, SECTION 5 'CROSS PRODUCT DEPENDENCIES', for more
  information and the Program Directory, Section 6.0, "Changes
  to Installation Procedures from DFSORT Rel 12.0:" (3rd bullet).
  .
  7- (10/23/95)
   ABEND0C4 OR ABEND0C6 AT +1016 INTO MODULE ICEIPUM AT REL 13.0
   LEVEL DOING A STORE OF R7 INTO R1 (BASE CODE). SORT IS INVOKED
   BY SAS BOOSTER. R1 HAS A BAD VALUE.
  This problem has been identified by SAS as being in their
  code. SAS is overlaying the blockexit parmlist that is pointed
  to by the DFSORT parmlist with control card images that SAS is
  generating. The customer needs to contact SAS Inc. for a fix.
  .
  8- (01/29/96)
   MSGCSV003I AND ABEND806-04 ISSUED AFTER INSTALLING DFSORT
   REL 13.0.
  The message CSV003I 'MODULE ICENLS NOT FOUND' and a ABEND806
  RC=04 is issued along with message ICE726I 'LOAD FAILED FOR
  LOCALE PROCESSING' after installing DFSORT R13.  This is due
  to the customer having a prior releases ICEMAC macros (ICEAM1-
  ICEAM4) installed in a library being picked up before the
  ICEMAC macro for Rel 13.0. You must delete these or remove
  the library they are in from the linklist.
  .
  9- (2/7/96)
   MSGICE083A UNAVAILABLE RESOURCES DYNALLOC (0218)
  This message is usually issued for one of two reasons.
  The first being that you have defined to the system devices
  that are physically not attached. The second is that the
  devices defined are mounted as PRIVATE and DFSORT requires
  PUBLIC access to those devices for use as dynamically
  allocated work data sets.
  ADDITIONAL KEYWORDS:
  ICE083A DYNALOC B37
  .
  10- (03/12/96)
     ***WARNING***
  For a COPY application, the SORTIN data set should not be
  the same as the SORTOUT data set or any OUTFIL data set be-
  cause this can cause lost or incorrect data or unpredictable
  results.
  For a SORT application, the SORTIN data set should not be the
  same as any SORTWKnn data set because this can cause lost or
  incorrect data or unpredictable results.  The SORTIN data set
  can be the same as the SORTOUT data set or OUTFIL data set
  but this situation can lead to loss of the data set if the
  SORT application does not end successfully.
  The above information is documented in the APG (SC33-
  4035-17), PP 53. Section Titled: General Coding Notes.
  .
  11- (3/22/96)
    WARNING MESSAGE ISSUED BY BINDER DURING PTF INSTALL
  Warning messages issued by Binder during installation of
  PTF UN88299 for DFSORT R12 (HSM1D00) for module ICEIPUT
  (NOTE: These messages can be IGNORED!):
  .
  IEW2322I
  1220 14 NAME ICEIPUT(R) IEW2646I 4B07 ESD RMODE(24) CONFLICTS WI
  WITH USER-SPECIFIED RMODE(ANY)
           FOR SECTION ICEDEVT0. IEW2646I 4B07 ESD RMODE(24)
           CONFLICTS WITH
  USER-SPECIFIED RMODE(ANY)
           FOR SECTION ICECYLN0. IEW2646I 4B07 ESD RMODE(24)
           CONFLICTS WITH
  USER-SPECIFIED RMODE(ANY)
           FOR SECTION ICEDYN10. IEW2646I 4B07 ESD RMODE(24)
           CONFLICTS WITH
  USER-SPECIFIED RMODE(ANY)
           FOR SECTION ICECYLPUSEREW2646I 4B07 ESD RMODE(24)
           CONFLICTS WITH
  USER-SPECIFIED RMODE(ANY)
           FOR SECTION ICECYLN0. IEW2646I 4B07 ESD RMODE(24)
           IN SECTION
  ICECYLN0 AT MODULE_OFFSET
           0001536D IN MODULE WITH RMODE=ANY CANNOT BE
           RELOCATED.
  .
  These messages are 'harmless' and have been fixed in REL 13
  (by supplying a RMODE card inside the source code for each
  effected module).
  .
  12 - (04/11/96)
   MSGICE818I ddname LOCATE SVC CALL FOR COMPIND FAILED - RETURN
   CODE x AND REASON CODE z.  OCCURS ON DFSMS 1.1.0 OR LOWER.
  DFSORT attempted to issue a LOCATE SVC for a VSAM data set
  but COMPIND was not introduced until DFSMS 1.2.0 and thus
  DFSORT could not retrieve the requested information from the
  data set. COMPIND is the directory name. The processing con-
  tinues without the information from the LOCATE SVC. This can
  result in the following actions:
   - DFSORT issues an error message and terminates if an empty
     VSAM data set was used.
   - DFSORT is unable to accurately estimate the size of an
     input data set.
  No action is required and this is only an infomational message.
  If DFSORT is unable to accurately estimate the file size,
  specifying a FILSZ option on the OPTION control statement may
  improve DFSORT's performance, especially when dynamically
  allocated work data sets are used.  More info on the RETURN
  CODE and REASON CODE can be obtained from refering to message
  IDC3009I in the 'SYSTEM MESSAGES, VOLUME 3'.
  KEYWORDS: ICE818I LOCATE COMPIND VSAM
  This message can be prevented on DFP 3.3 systems through
  application of the appropriate PTFs to the following DFP
  COMPIND toleration APARs:
  
    OW00314
    OY67925
    OW03916
    OW04155
    UW05205
  .
  13 - (5/16/96)
  The following BINDER messages may be received when installing
  the support for the SORTREC command under ISMF, and may be
  ignored:
      IEW2646W xxx ESD RMODE(24) CONFLICTS WITH USER-SPECIFIED
               RMODE(ANY) FOR SECTION ICEPDV01
      IEW2651W XXX ESD AMODE 24 CONFLICTS WITH USER-SPECIFIED
               AMODE 31 FOR ENTRY POINT ICEPSR01
      (MSGIEW2646W,MSGIEW2651W)
      Note: Both of these modules should be RMODE(ANY) AMODE31.
  14) Loop in ICEISAM or ICEXPUB issuing SVC31 (0A1F). Customer
      was using CA1 (CA90) and dataset was an empty compressed
      ps. Compression supplied by BMC's DATAPACKER.
      RESOLUTION: CA1 Fix number: GO68336
      Note: Customer also applied Candle Corp's fix T5ZS177
  15) For customers who need to modify the runtime options
      when DFSORT is called by programs written in high-level
      languages, such as PL/1 or COBOL, there are only a limited
      number of options that may be specified on the SORT control
      statement. Customers may use the DFSPARM statement, as it
      can be used to control an extended list of options,
      DSPSIZE and HIPRMAX.  For additional information on this
      topic, please see the Application Programming Guide,
      pages 26-44, 222-229,and 497.
      Additional keywords: VLR FB.
  
  16) An ABEND0C4 can occur if R12 & R13 are installed in
      resident mode on the same system, even when different
      SVCs and steplibs are used to access the R13 libraries.
      The current design of DFSORT does not allow for the testing
      of 2 releases of DFSORT installed in resident mode on the
      same system.
  17) EQUALS NOEQUALS EQUALS=YES EQUALS=NO
      When migrating from a previous release of DFSORT to
      R13, users have reported that they observed duplicate
      records in a different order on output than was produced
      under a previous release of DFSORT. In both instances
      NOEQUALS (EQUALS=NO) was specified or used as the default.
  
      If NOEQUALS (EQUALS=NO) is specified, then the user is
      telling DFSORT that the output order for duplicate records
      is not important. Users who need records to be in a
      particular order should specify EQUALS=YES, or add an
      additional sorting key to force the desired outcome.
  
      NOTE: It is possible to see variations on output even
      within a release depending upon maintenance level.
  

Local fix

• KEYWORDS:
  5740SM105 INFOAPAR INFO APAR RF00 RD00
  

Problem summary

Problem conclusion

Temporary fix

Comments

• This is a dummy 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