IOFTech    Maintenance   Release8G       Newsletters    Doc    FAQ    Contacts    Home    Webmaster

IOF Problem Resolution
Problem D01
Previous Next
Description Clist or Rexx exec terminates with an error message. (SLAMRUN, SLAMMEMO, SLAMARCH, SLAMOPER, OUTQUE, IOFWTR, IOFCLNDX, JAROPEN, JAROFFLD, JARCLOSE or locally written clists or commands).
 
Background Many IOF clists and Rexx execs execute IOF from batch TSO. An IOF user environment is established for the batch job or started task. The task is assigned to an IOF group and is controlled just as a TSO user would be controlled.

Output from batch TSO sessions that would normally be written to the TSO screen are redirected to the SYSTSPRT data set which is usually a sysout data set. This data set, along with the Job Console Log and the System Messages data set contain information useful in diagnosing batch TSO problems.

Many of the distributed IOF clists and Rexx execs are designed to be executed in batch TSO. This clists/execs list important session attributes in SYSTSPRT for diagnostic purposes. For example, SYSTSPRT from a SLAMRUN session has the following information:

SLAMRUN Clist version: T8A

SLAMRUN 10/24/02 08:15:16 Product level: 8A.0 Date: 09/26/02 Time: 09

SLAMRUN SLAM Variables Display SLAMRUN Name-----Value----From--------Option---Description-------------- SLAMRUN USERID SLAMRUN SESSION Userid of this session SLAMRUN GRPNAME STCGROUP SESSION B23ALLOW IOF Group name SLAMRUN ASCBTYPE STC SESSION Job, TSU, or STC SLAMRUN ACCT SESSION Account code SLAMRUN XEQSYSID TSI1 SESSION Execution system id SLAMRUN INTRFACE BATCH SESSION IO interface type SLAMRUN ACFGROUP SYS1 SESSION RACF connect group SLAMRUN A19NODEN TRISYS SESSION Session node name SLAMRUN SLMJOBNM SYSLOG OPTIONS B30SLAM Name of the SYSLOG task SLAMRUN SLMSYSID YES OPTIONS B30SLAM Sysid in SLAM index DSN SLAMRUN SLMEMOJN SLAMMEMO OPTIONS B30SLAM SLAMMEMO jobname SLAMRUN SLMINDEX YES OPTIONS B30SLAM Index the system log SLAMRUN IOFLEVEL 8A SESSION IOF level SLAMRUN IOFSPIN 2005011 OPTIONS IOF spin level SLAMRUN SIPREFIX SYSIOF OPTIONS B32INDEX Default index DSN prefix SLAMRUN SISUFFIX IOFINDEX OPTIONS B32INDEX Default index DSN suffix SLAMRUN GRPPAUSE 0 SESSION B23ALLOW Minimum pause SLAMRUN GRPEXTND YES SESSION B23ALLOW Extend option

SLAMRUN 10/24/02 08:15:17 Index DSN is SYSIOF.SYSLOG.$TSI1.IOFINDEX.

The session USERID, IOF GROUP name, IOF level, IOF CLIST library level, and index data set name are shown. This information can be useful in diagnosing problems.


 

Checks Review the following sysout data sets from the job or task:
  • SYSTSPRT. Check for IOF error messages.
  • LOG (Job Console Log) Check for MVS or security system errors.
  • MESSAGES (System Messages) Check for MVS allocation or other errors.


 

Information IOF displays short error messages on the right side of the top line of the display. Pressing the HELP key (PF1) causes the long error message to be displayed on the second line of the display. Many IOF batch TSO clists and Rexx execs detect IOF error conditions and automatically display the long error message in SYSTSPRT.

IOF error messages are generated based on function return codes. To determine the short and long error messages associated with IOF return code nnnn, enter "ERROR nnnn" on any IOF panel. The short error message will be displayed. Press the HELP key (PF1) to display the long error message.

Batch TSO jobs are subjected to the same access control rules as normal TSO sessions. Analyze the IOF error messages as if they were displayed at a normal TSO session, and take the same action to correct the error.


 

Information The batch TSO clist or Rexx exec may be running the wrong version of IOF. If you use a STEPLIB or ISPLLIB in you TSO LOGON procedure to access the current version of the IOF and IOFSPF load modules, then a STEPLIB may also be required in the batch TSO JCL.

Many of the supplied CLISTs and Rexx execs display diagnostic information in the SYSTSPRT data set. Included in this information is the IOF VERSION being used.

It is good practice to use the IOF CLIST and LOAD libraries from the same version of IOF. Some clists and execs will not function properly with different IOF versions.
 

More Help Click here to EMAIL a problem report to IOF Technical Support for additional assistance.

 

Previous Next

Triangle Systems, Inc. PO Box 12752, Research Triangle Park, NC 27709
(919) 544-0090

IOFTech    Maintenance   Release8G       Newsletters    Doc    FAQ    Contacts    Home    Webmaster

Monday, 25-Jan-2016 13:45:29 EST
[an error occurred while processing this directive]

cbatds ibterrs sbatstep @@