PQ01919: " /FORMAT MODNAME " COMMAND FROM A PF KEY REJECTED WITH DFS1267

APAR status

• Closed as Permanent restriction.

Error description

• " /FORMAT modname " command entered via a PF KEY is rejected
  with DFS1267 'PARAMETER CONTAINS INVALID CHARACTERS'.
  

Local fix

• Add a period after the modname in the /FORMAT command.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: IMS 5.1 users entering /FORMAT commands      *
  ****************************************************************
  * PROBLEM DESCRIPTION: /FORMAT command rejected with DFS1267   *
  ****************************************************************
  * RECOMMENDATION: Install local fix available from IBM.        *
  *                 Fix name: IMS 6.1 - RQ01919B.                *
  *                 Fix name: IMS 7.1 - RQ01919C.                *
  *                 Fix name: IMS 8.1 - RQ01919D.
  *                 Fix name: IMS 9.1 - RQ01919E.
  *                 Fix name: IMS V10 - RQ01919F.
                    Fix name: IMS V14 - RQ01919J
  ****************************************************************
  " /FORMAT modname " command is rejected with:
  DFS1267 " PARAMETER CONTAINS INVALID CHARACTERS ".
  
  This problem is due to the user MFS format defining the cursor
  field to be passed to IMS as part of the input.  Therefore, when
  MFS formats the input data, the cursor position data (00050019)
  is placed immediately following the first input field, which is
  normally a transaction or user data.
  
  In the failing case, the first input field is a "/FOR modname"
  command, so the MFS formatted data stream passed to IMS is:
  
                    61C6D6D940E3C5E2E3400050019
                    / F O R   T E S T   .......
  
  
  The IMS command parser module , DFSICL30, rejects the command
  because the cursor position data '00050019' is not alphameric.
  
  IMS releases prior to IMS 5.1 ignored any non-alphameric data
  and therefore ignored the cursor position data '00050019', which
  resulted in successful processing of this /FORMAT command.  In
  IMS 5.1 and above, the cursor position data is considered
  invalid.  In this case, a period following the modname, TEST,
  would signal the command parser to ignore any data beyond the
  period.
  
  However, through the years, IMS control region outages occurred
  because modules given control from the command parser were
  passed invalid data.  Those modules did not contain data
  validation routines because the expectation is that the command
  parser would perform that validation on their behalf.
  
  Therefore, in IMS 5.1, the command parser module was enhanced to
  detect any invalid input data, and reject the command in order
  to avoid a potential IMS outage.
  

Problem conclusion

• The problem can also occur when the /FOR command is entered
  directly from the terminal or entered via a PF KEY.
  
  The user should simply add a period to the end of the command to
  separate it from additional unwanted data as stated in the
  OPRM:  "If you do not enter a period, residual data from a 3270
  affects command processing".
  
  Since some customers enter the /FOR command through a PF key
  definition in their MFS formats, this same solution of adding
  the period might involve modifying thousands of formats.  A
  USERMOD is being provided by IBM an alternative to modifying
  these formats.
  
  IMS development will supply a code change to the IMS command
  parsor module, DFSICL30, to resolve the problem with the IMS
  /FORMAT command rejected with DFS1267.
  
  Terms and conditions:
  
    * The code will be given to the customer in SMP-installable
      format as a ++USERMOD. Contact the IBM-IMS support center
      and request fix:
          Fix Name   Release  Comp ID    FMID
          ======================================
          RQ01919A - IMS 5.1  569517611  HMK5100
          RQ01919B - IMS 6.1  565515800  HMK6600
          RQ01919C - IMS 7.1  5655B0100  HMK7700
          RQ01919D - IMS 8.1  5655C5600  HMK8800
          RQ01919E - IMS 9.1  5655J3800  HMK9900
          RQ01919F - IMS V10  5635A0100  HMK1010
          RQ01919J - IMS V14  5635A0500  HMK1400
  
    * The customer is responsible for maintaining the code as a
      usermod from an SMP viewpoint.
  
    * The code will be supported by IBM to the extent that if a
      problem occurs with the code applied, IBM will resolve that
      problem and subsequently revise and redistribute the code
      if necessary.
  
    * The code will never be permanently integrated into the IMS
      product, hence this apar is closed PRS-Permanent Restriction
  

Temporary fix

Comments

• Repinned 01/11/2006 to add V9 usermod RQ01919E
  Repinned 08/12/2008 to add V10 usermod RQ01919F
  Repinned 06/22/2018 to add V14 usermod RQ01919J
  

APAR Information

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

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

Modules/Macros

•    NA
  

Fix information

Applicable component levels