JR32318: SOURCETOTARGET (JOB SOURCETOTARGET) FINISHED, STATUS=96

APAR status

• Closed as fixed if next.

Error description

• Whilst the overall behaviour is different between Windows and
  UNIX the problems caused by this are common to both platforms.
  If you check the userstatus in the job report section you would
  find it is truncated to 'f:' on both platforms. The difference
  in behaviour is caused by the difference in behaviour of the
  construct kill(0,0) on the two platforms, on windows this
  returns -1 and thus asserts the job being waited on has gone
  away (crashed). On UNIX it returns 0 thus the code thinks the
  child is still alive and waits for the correct termination code.
  The PID of zero comes about because the '\' characters in the
  user status make a mess of the returned jobinfo which has '\'
  separated fields.
  
  The obvious workaround is to not use the '\' character in the
  user status field
  

Local fix

• do not use the \ backslash
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  SERVER
  ****************************************************************
  PROBLEM DESCRIPTION:
  The user status for a job is not documented as having a
  restriction on the characters that can be used, however '\' is
  problematic as it is used to separate a number of entries in the
  status list returned from a repository call
  ****************************************************************
  RECOMMENDATION:
  Fixed in release 8.2
  ****************************************************************
  

Problem conclusion

Temporary fix

Comments

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

• R752 PSN

     UP

• R753 PSN

     UP

• R801 PSN

     UP

• R810 PSN

     UP