II07978: ISPF V4.*, COMMON USAGE PROBLEMS.

APAR status

• Closed as canceled.

Error description

• This INFORMATIONAL APAR is for
  ISPF VERSION 4 RELEASE 1 MOD 0
           COMPID :  565504201 (ISPF) and  565504202 (PDF)
           FMIDS  :  0568126   (ISPF) and  0568127   (PDF)
           RELEASE:  102       (ISPF) and  103       (PDF)
      ISPF VERSION 4 RELEASE 2 MOD 0
           COMPID :  565504201 (ISPF) and  565504202 (PDF)
           FMIDS  :  0568126   (ISPF) and  0568127   (PDF)
           RELEASE:  202       (ISPF) and  203       (PDF)
  This APAR deals with the Common Usage Problems associated
  with ISPF V41 reported to the support center.
  RELATED INFO APARS:
    II07895 - ISPF CLIENT/SERVER APPC PROTOCOL INFORMATION
    II07897 - ISPF CLIENT/SERVER TCP/IP PROTOCOL INFORMATION
  ----------------------------------------------------------------
  KEYWORDS: ISPFINFO PDFINFO V41 V4R1 V4R1M0 R102 R103
  ----------------------------------------------------------------
  PROBLEM:
    SMP/E "START" results in SPLIT SCREEN and X-Clock.
    ISPF V4.1 added a New Command "START",  this command
    is picked-up rather than SMP/E's START command for
    SUSPEND PROCESS.
  CURRCUMVENTION/FIX:
    Create a CMDS table via OPT3.9 for the NEWAPPL that
    SMP/E is invoked with. Add an entry for COMMAND of
    START, with ACTION of PASSTHRU.
    SMP/E APAR IR26524 - will address the SMP/E Command Table.
    ISPF  APAR OW04954 - will address the X-Clock / wait problem.
  
  DATE ADDED:   6/15/94  RMS
  ----------------------------------------------------------------
  PROBLEM:
    User modified ISPF DTL sourceand is unable to recompiled
    the ISPF DTL due to errors(ie. restricted attributes in the
    x'00' to x'2f' range ).
  CURRCUMVENTION/FIX:
    The Planning and Customizing Manual references recompiling
    ISPF DTL source, see pages 23 and 43 of Chapter 2.
  
    NOTE: The KEYAPPL parameter or the Keylist Application ID
          field must specify ISR as the applid for ISPF DTL
          source.
  
  Date added 6/21/95 GHC
  ----------------------------------------------------------------
  PROBLEM:
  User is going between V3R5 & V4R1 and uses opt3.2 or opt3.4
  and gets msg ISPV006 stating that variable ZAL1EX is too long.
  (msg can occur for various variable names and options)
  CIRCUMVENTION/FIX:
  SC34-4443-00 V4R1 PLANNING & CUSTOMIZING manual on pg XVI
  under the title MIGRATION CONSIDERATIONS notes that you must
  use separate profiles when running between previous version/rel
  of ISPF/PDF and V4R1
  ADDITIONAL KEYWORDS:
  ZAL2EX MSGISPV006 OPT32 OPT34
  
  Date added 6/28/94 HBC
  ----------------------------------------------------------------
  PROBLEM:
   Unable to get TSO Session Manager TSOUT mode to work from ISPF.
   Session Manager responding in line mode from OPT6 , ISRTSO .
  CIRCUMVENTION/FIX:
   - Check OPT0, panel ISPISMMN, has selected SESSION MANAGER:
                 Select Options:
                   Enter "/" to select option
                   /  Command line at bottom
                      ...
                   /  Session Manager mode
  
   - If you are running with an old/previous version ISPF profile
     there are ZSM* variables defined in it (ref. APAR OW06062)
     The following Rexx Exec can be used to clean these up:
       /* Rexx */
       Address ISPEXEC
       'VERASE (ZPDFREL)  PROFILE'
       'VERASE (ZSM)      PROFILE'
       'VERASE (ZSESS)    PROFILE'
       'VERASE (ZICFPRT)  PROFILE'
       'VERASE (ZCUNIT)   PROFILE'
       'VERASE (ZFLMTPTR) PROFILE'
       'VERASE (ZFLMTLEN) PROFILE'
       'VERASE (ZFLMNLST) PROFILE'
       'VERASE (ZFLMTRMT) PROFILE'
       Exit
  
  Date added 2/03/95 RMS
  ------------------------------------------------------------
  PROBLEM:
    Message ISPP605 (the SELECT WSCMD service is only valid when-
    in GUI mode) is received when a TSO command is entered under
    OPT6 when running ISPF in NON-GUI mode. If the command is
    prefixed with " TSO " it works fine.
    One possible cause is that the Workstation  command was
    selected from the FUNCTIONs Action Bar when the ISPF session
    was running in GUI mode.
  CIRCUMVENTION/FIX:
    Under the Functions action bar - Select setting 2 -
    TSO command - Sets the command shell to route commands to TSO.
  NOTE:
    Any command may be prefixed with either "TSO" or "WS" to
    override the command function setting.
  ADDITIONAL KEYWORDS:
    MSGISPP605 MSISPP605 INVALID SERVICE
  
  DATE ADDED:   2/07/95  BMM
  ----------------------------------------------------------------
  PROBLEM:
    ISPD241 , "Invalid option " ,
              "The option that was entered was not valid."
    Command line has ISRROUTE ... specified.
  CURRCUMVENTION/FIX:
    You are running with a pre - V4.1 ISPCMDS table.
    Remove your old copy of ISPCMDS from the ISPTLIB concatenation
    ISRROUTE is one of several new commands to ISPF V4.1 .
  KEYWORDS:
    COMMAND MSGISPD241 ISROUTE
  Date added 7/20/95 RMS
  ------------------------------------------------------------
  PROBLEM: *** THIS PROBLEM ONLY EFFECT V4.2 ISPF
   Various File Tailoring Failures, because Skeleton 'ISR*'
   COULD NOT BE FOUND.
   EXAMPLES -
     OPT 3.14 ( OPT314 ) message ISRS110 is received
       when attempting to search, 'File tailor failure'
       'File tailoring of member selections failed.'
     OPT 3.6 ( OPT36 HARDCOPY ) message ISRU107 is received
       when attempting to print, error box is displayed because
       ISRUHCS* is not found.
     OPT 3.8  ( OPT38 OUTLIST ) message ISRU291 is received
       when attempting to print, 'Job skeleton not found'
       'Job card skeleton "ISRSCHPJ" was not found.'
  CIRCUMVENTION:
    ISPSLIB DD card is missing data set 'ISP.V4R2M0.SISPSLIB'.
    in it's concatenation. This data set is NEW with V42
    ISPF/PDF .
  KEYWORDS
    HARD COPY OUT LIST OPT3 SKELS SISPSLIB ISPSLIB V42
  Date added - 10/12/95 rms
  

Local fix

• RMS 7/20/95
  RMS 6/15/94
  GHC 6/21/94
  HBC 6/28/94
  RMS 2/03/95
  BMM 2/07/95
  ----------------------------------------------------------------
  PROBLEM:
  Colour changes to the ISPF Calender from the default cause the
  TAB to POINT and SHOOT ( PNTS ) to stop working on ISR@PRIM.
  CIRCUMVENTION/FIX:
  Problem is caused by updates to ISPCAL and ISPCALCG which also
  require ISR@PRIM to be updated. Many customers have a modified
  ISR@PRIM in their ISPPLIB concatenation prior to the IBM
  shipped one. Solution is to rebuild the customer's ISR@PRIM
  based on the IBM supplied version.
  eg: UW20283, UW20284 and UW20285 can expose this problem
  if ISR@PRIM does not reflect the changes in UW20283.
  Date added 2/15/96 PRO
  -----------------------------------------------------------+---
  PROBLEM:
   The following text is found on panel ISPSM200 in IPSF V4.2..:
  "You may select any or all of the following options by
  entering a non-blank character in the input field preceding
  the text (3270 display mode) or by checking the box (GUI
  mode). To de-select an option, type a blank in the input
  field preceding the text (3270 display mode) or unchecking
  the box (GUI mode)."
   This can be misleading as it refers to the SETTINGS
  panel ISPISMMN and not the Tutorial panel on which it
  is found.
  Date added 03/01/96 PVM
  --------------------------------------------------
  Problem:
   ISPV006 for SPDATC when using WORKLOAD MGR.
   *****************************************************
    Data truncation occurred
    Data for CHAR format variable "SPDATC" was too long.
  ...
    A severe error occurred under dialog:
        Application:      IWMP
        Function:         Module    IWMA2SDI
        Service:          TBSKIP
    Error message ID:     ISPV006
    *************************************************
  Solution/Fix: Need to apply WorkLoad Mgr fix UW23912
                to failing system.  Table was created on a
                system that had UW23912 applied.
  Keywords    : IWMARIN0 MSGISPV006 VDEFINE TRUNC
  Added by - RMS 5/02/96
  ---------------------------------------------------------------
  Problem: Batch or Foreground invocation of ISPF terminates
           with error message of :
          ISPT017 - I/O ERROR ON GET
       or ISPP151 - ISPP151 Panel 'aaaaaaaa' error - I/O error...
       followed by :
         A dialog error has occurred before the dialog manager...
         IKJ56641I ISPF     ENDED DUE TO ERROR+
         IKJ56640I USER ABEND CODE 0998  REASON CODE 00000000
  SOLUTION/FIX:
     Commonly seen with V4.2 of ISPF.
     The ISPT017 is seen when the first data set allocated to
     the ISPTLIB DD is a dynamic allocation ( temp ) and the
     ISPP151 is seen with the first data set allocated to the
     ISPPLIB DD is a dynamic allocation AND the blocksize
     for this dynamic allocation is less than the 8800 blocksz
     of the V4.2 ISPF data sets.
     The blocksize specified for the dynamic allocation will
  need to be change or the ACS routine will need to be changed
  to 8800, so that concatenated data set blocksizes are equal
  to or smaller than this blocksize.   V4.2 Table and Panel
  data sets are shipped with a blocksize of 8800.
  References:
  JCL Reference, MVS v5, GC28-1479, Chapter 12,
  'Concatenating Data Sets'
  ...
  Block Sizes for Concatenated Data Sets:  Concatenated data sets
  can have different block sizes.  In a few cases, the data sset
  with the largest block size must appear first in the concaten-
  ation. ( Note that you can state a value equal to the largest
  Block size for BLKSIZE on the first DD statement, regardless of
  what the actual block size of the data set is.)
  DFP V1.3 'Using Data Sets', SC26-4922-02
  Chapter 26 'Processing a Sequential Data Set',
  under 'Concatenating Like Data Sets' :
  ...
  * If you code the BLKSIZE parameter in the DCB macro or on the
    first DD statement, then the block size of each dat set must
    be less than or equal to that block size.
  ...
  Chapter 22, 'Specifying and Initializing a Data Control Block',
    heading of 'OPEN--Preparing a Data Set for Processing':
    Figure 73, shows the precedents of the DCB information,
    DCB -> JFCB -> DSCB1 (label) for the default blocksz .
  KEYWORDS: BLOCK SIZE BLKSIZE BLOCKSZ BACKGROUND BATCH FORGROUND
    LARGEST BLOCKSIZE FIRST DPF31
  ADDED by - RMS 5/30/96
  --------------------------------------------------------------
  PROBLEM: File transfers using IND$FILE do not work in
      option 6 ( ISPF Command Shell ).
  CIRCUMVENTION/SOLUTION:
      The ' Tab to point-and-shoot fields ' setting in the
      ISPF Settings panel must be unselected.  Generally
      IND$FILE tries to put the command in the last entry
      field of the panel.  Due to 3270 architecture, the
      'Tab to point-and-shoot fields' option makes the
      saved commands input fields.
  KEYWORDS: xfer send receive
  Added 08/30/96 by DGN
  ------------------------------------------------------------
  Problem:  Confusion regarding never-expire date in option
            3.2 allocation
  (1) Through the PDF OPT3.2A and M,
      the never expire date of '99.366' is not allowed, The
      'ISRU253 DATE NOT ALLOWED' error message is expected.
      The following dates can be used as a never expired date.
        - 99.365
        - 1999.365
        - 1999.366
        - 99/12/31
        - 1999/12/31
  (2)Through the PDF OT3.2A, for the expiration date specification
     you can specify a DDD value of up to 366 if the YY or YYYY
     value represents a leap year.
     1999.366 is accepted as an exception to the leap year rule.
  (3)After the YR2000, you can still use the above dates as a
     never expire date even if the PDF Configuration table value
     of CHECKEXP is YES
  

Problem summary

Problem conclusion

Temporary fix

Comments

• Closing 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