JR54733: IS 11.3. SEQUENCER ALLOWS AN INVOCATION ID FOR A JOB WHEN IT IS PASSED VIA A PARAMTER. DIRECTOR DISPLAYS RUN-TIME ERROR 5

APAR status

• Closed as fixed if next.

Error description

• Information Server 11.3. If a multi-instance job is run via a
  sequence and the job's invocation ID is a parameter, DataStage
  allows the sequence to pass an invocation id with special
  characters, example 1A,2B. When the job is run, the director
  immediately errors with
  Run-time error 5
  Invalid procedure call or argument
  
  The Director will then error every time it is open until the job
  is recompiled or the config file is cleared.
  

Local fix

• recompile the job. Dont use special characters in the invocation
  id
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Use of Job Sequencer to initiate jobs supplying Invocation Id as
  a parameter
  ****************************************************************
  PROBLEM DESCRIPTION:
  When a sequence calls a job using an invocation id that contains
  a comma, a run time error results
  ****************************************************************
  RECOMMENDATION:
  Invocation IDs should consist of alphanumeric and underscore
  characters only. The job sequencer will be modified to prevent
  use of other characters, as the Director already does. APAR
  raised for future fix.
  ****************************************************************
  

Problem conclusion

Temporary fix

• Recompile the job. Dont use special characters in the invocation
   id
  

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

• RB50 PSY

     UP