Sun Mainframe Batch Manager Software, Release 10.1.0
Updated User Documentation

This file contains updates to the user documentation
released with MBM 10.1.0. If there are no documentation
updates for a patch release, it is so noted.

Note: The acronym CR followed by a number stands for Change Request.

--------------------------------
MBM 10.1.0p1 - 120077-01
--------------------------------

Important Operating Information

1. Sun MBM 10.1.0, with a minimum patch level of 1, is now supported on the
   Solaris(tm) 8 Operating System (OS). 

2. Do not use the batch_shut or batch_start commands.  These commands are used
   internally by the bam process for starting and stopping nodes. If you invoke
   these commands directly, thread and class configuration information is lost. 
   To manually start or stop a node from the command line (or from a script),
   you must use the 'bam startbatch' or 'bam stopbatch' commands. Using the 
   'bam' commands retains the thread and class configuration information. 
   (CR 6254928)

3. Refer to $PUBLIC/bin/cblmake.sh for the COBOL options needed by Sun MBM. 
   Refer to your COBOL documentation for a description of these options. 
   (CR 6272786)

Enhancements

1. When you create a subsystem using the Batch Administration Manager (BAM),
   Sun MBM now automatically sets the environment variable MBMSUB in the 
   subsystem setup file. This variable identifies the directory from which you 
   execute the mvstrans or dostrans command. For example, if you are translating
   MVS JCL, the $MBMSUB directory is the parent of the jmvs, mvsp, and ish
   directories. Using this new environment variable, you can quickly change to
   the $MBMSUB directory and start validating or translating JCL. (CR 4668973)

2. Support for the External Call Interface (EXCI) has been enhanced to include a
   new COBOL preprocessor that generates the COBOL code from the EXEC CICS LINK
   call. New documentation includes the syntax of the excitrans command
   and new error messages. (CR 5031695)

   excitrans COBOL Preprocessor

   The excitrans preprocessor replaces EXEC CICS LINK calls with the appropriate 
   CALL 'ebmexci' call.  excitrans also inserts a comment before any 
   CALL 'DFHXCIS' calls to warn of an unsupported action.

     Format:
      excitrans -d <infile> [<outfile>]

     where:
      -d         :  Turns debugging on
      infile     :  The input file
      outfile    :  The output file; defaults to standard out (stdout)

   Error Messages

   BS9005(E) CALL 'DFHXCIS' is not supported in this release.

     Description: The COBOL application contains an unsupported CALL 'DFHXCIS'
     statement.
 
     Solution: Recode the EXCI statement as an EXEC CICS LINK statement.

   BS9006(E) Error (%d) opening input file %s.

     Description: An error occurred (%d) when the excitrans preprocessor 
     attempted to open the input file.

     Solution: Check the permissions on the input file and verify that the
     spelling of the input file name is correct.

   BS9007(W) Error (%d) opening output file %s.  Output redirected to stdout.
    
     Description: An error (%d) occurred when the excitrans preprocessor 
     attempted to create the output file.

     Solution: Check the permissions on the output file and verify that the
     spelling of the output file name is correct.

   BS9008(E) Option -%c requires an operand
    
     Description: The specified option was passed to the excitrans preprocessor
     without an operand, which is required.

     Solution: Refer to the excitrans documentation for the correct usage of the
     option.

   BS9009(E) Unrecognized option: -%c
     
     Description: An incorrect option was passed to the excitrans preprocessor.

     Solution: Refer to the excitrans documentation for the correct usage of the
     option.

   BS9010(E) Unrecognized option: %s.
     
     Description: An incorrect option passed to the excitrans preprocessor.

     Solution: Refer to the excitrans documentation for the correct usage of the
     option.

   BS9011(E) Input file is required.
     
     Description: The excitrans preprocessor requires an input file name.

     Solution: Refer to the excitrans documentation for the correct syntax.

   BS9012(E) Buffer overflow detected. Cannot copy more than %d characters.
   Parameter truncated to %s.

     Description: A buffer overflow was detected and avoided.

     Solution: Shorten the length of the parameter to %d bytes.

   BS9013(E) Unexpected null character on line %d, converted to ' ' : %s
     
     Description: A null character was found in the input stream and was 
     converted to a space.

     Solution: Remove the null characters in the source program.

   BS9014(E) Syntax error at or near keyword %s

      Description: A syntax error occurred near the specified keyword.

      Solution: Locate the syntax error in the EXEC CICS LINK command, and
      correct it.


Fixed Problems

1. A fix to CR 6265013 resulted in a new error message. This fix corrects a
   problem which could cause mvstrans to dump core when a <procstep>.<stepname>
   exceeded 17 characters.

   MV0692(W) Line=#%3.3d. Label %s is too long. It will be truncated to %d
   characters.

     Description: On the specified line of the JCL, the label exceeded the 
     maximum number of characters. The label will be truncated to the specified
     number of characters.

     Solution: Shorten the label name so that the length does not exceed the
     specified number of characters.

2. A fix to CR 6270061, which relates to the EXCI implementation, resulted in
   the following change to the Sun MBM Migration Guide. Code example 9-1 is
   incorrect. 
   Lines 1-9 of the code example should be as follows:

   WORKING-STORAGE SECTION.
    01 WS-EXCI-RETURN-CODE-AREA.
      05 WS-EXCI-RC.
        10 WS-EXCI-RC-RESP PIC S9(08) COMP.
        10 WS-EXCI-RC-RESP2 PIC S9(08) COMP.
        10 WS-EXCI-RC-ABCODE PIC X(04).
        10 WS-EXCI-RC-MSGLEN PIC S9(08) COMP.
        10 WS-EXCI-RC-MSGPTR POINTER.

3. If you are using CoSORT Version 8, you must set sort parameters as described
   here. The information in the Sun MBM Migration Guide only applies if you are
   using CoSORT Version 7 and earlier. (CR 6288254)

   You must set all sort parameters in their proper order, as documented by
   CoSORT, in the SYSIN file. Sun MBM does not attempt to string together
   parameters for the "sortcl" invocation.

   Note - If the SYSIN containing the sort parameters is INSTREAM, you must
   "escape" the dollar sign character of environment variables by using the
   backslash character (\).  For example: 

   /INFILE(\$DD_SORTIN)

4. A fix to CR 6254197, which corrects a problem where the Sun MBM sortx
   utility abended if the SORTIN and SORTOUT files were the same, resulted in
   a documentation change. The second rule in the section "sortx Usage Rules" in
   Chapter 7 of the Sun MBM Migration Guide is no longer true. The new rule is:

   If the input file is a file system (FS) file, you can direct the output file
   to the input file. If the sort is successful, the input file is replaced with
   the output results of the sort. If the sort fails, the input file remains
   unchanged.

5. A fix to CR 6254199, which corrects a problem where the Sun MBM sortx
   utility abended if the SORTIN was not specified, resulted in an additional
   rule for the section "sortx Usage Rules" in Chapter 7 of the Sun MBM
   Migration Guide. The new rule is:

   If the SORTIN file is missing or not defined (there is no DD_SORTIN), Sun MBM
   defines SORTIN as /dev/null, and the sort continues. The result of the sort 
   in an empty SORTOUT file.

