Sun Mainframe Batch Manager Software, Release 10.0.1
Updated User Documentation

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

--------------------------------
MBM 10.0.1p2   -  117630-02
--------------------------------
1. Special Characters in SyncSort Control Statements (BugId 5045333)

A dollar sign ($) has specific meaning, at times, to the UNIX shell, as well as
to the Sun MBM engine. Therefore, use the following guidelines if the character
is being used in SyncSort parameters such as: /derivedfield  d1 "$".

- If the SYSIN file for the SyncSort parameters is a disk file, to maintain a
  $ character, you must either enclose the dollar sign in double quotes, or 
  use a single escape character (backslash) before the dollar sign. 
  
  For example, either format is acceptable:
  
  /derivedfield d1 "$"
  /derivedfield d1 \$
  
- If the SYSIN is instream, you must use three escape characters before the
  dollar sign, or enclose an escaped dollar sign in double quotes.
  
  For example, either format is acceptable:
  
  /derivedfield d1 \\\$
  /derivedfield d1 "\$"
  

2. A fix to BugId 5080773 resulted in the following new documentation:

   User utilities can be used to encapsulate any user-specific functions within
   macro execution. 
   
   All user utilities must assign a numeric return status in the file 
   status.${JON}. The status code must be in the range of 0-255. 
   
   For example, if the user utility is to return a zero or non-zero status 
   depending on the existence of the file named myfile, the setting of the
   exit status in a UNIX shell script would be similar to the following:
   
     ...
     if(-f myfile)
     then
        echo 0 > status.${JON}
     else
        echo 1 > status.${JON}
     fi
     ...

   A zero value indicates that the utility ended normally. A non-zero value 
   indicates that the utility ended abnormally and the job step will abort.

   The EXECPGM macro initializes the COND-CODE with a value of 255 before 
   calling user utilities. If the value in the status.${JON} file is not set
   to zero on normal termination, the step will abort due to the initial 
   non-zero value (255).

   The value set in the status.${JON} file will be the COND-CODE value of the 
   step.
   

3. A fix to BugId 5050041, which related to spurious messages that were 
   displayed if all GDG occurrences did not exist, resulted in the following
   new error message:

   MA2139(S) Internal error: Copy failed
   From file: %s
   To file: %s
   Return status: %d
 
     Description: An internal error was detected while attempting to copy a
     temporary work file.

     Solution: Contact your authorized service provider.

4. A fix to BugId 5088282 resulted in a new error message, which alerts you to
   a missing file in a concatenated dataset that is being processed by the
   IEBGENER utility.
   
   MA2568(S) Error accessing file: %s, errno=%d
   
     Description: While trying to perform an I/O on the specified file, a
     system error occurred. The operation is not specifically identified. In
     the error message, %s is the name of the file being operated on. It can
     also be a list of concatenated file names delimited by colons.
     
     Solution: Determine the type of error that occurred by mapping the 
     errno value in the message to the list of UNIX errors in the errno.h
     include file. For example, an errno=2 maps to "File not found". It 
     would indicate that the file named in the message was not found for
     an open or stat operation. In the case of a concatenated file list, 
     you must evaluate each file in terms of the error condition to
     determine which file caused the error. Verify that the file exists and 
     rerun the job.

--------------------------------
MBM 10.0.1p1   -  117630-01
--------------------------------
None

