Duplicate ad-hoc prompt number

You issue a job or Job Scheduler that is dependent on an ad-hoc prompt, but conman cannot submit the job because the prompt number is duplicated.

Cause and solution:

On the master domain manager, prompts are created in the plan using a unique prompt number. This number is maintained in the file of the master domain manager. JnextPlan initially sets the prompt number to "1", and then increments it for each prompt that is to be included in the plan.

If you want to submit a job or Job Scheduler using an ad-hoc prompt on another IBM Workload Scheduler agent during the currency of a plan, the local conman looks in its own runmsgno file in its own <TWA_home>/TWS/mozart/ directory, and uses the number it finds there. The value in the local file does not necessarily reflect the current value used in the Symphony file. For example, when the file is first created on an agent the run number is created as the highest run number used in the Symphony file at that time, plus 1000. It is then incremented every time conman needs to assign a number to a prompt. Despite this interval of 1000, it is still possible for duplicates to occur.

To resolve the problem, edit the file and change the number. An example of the file contents is as follows: 
         0       1236
The format is as follows:
  • The 10-digit last Symphony run number, right-justified, blank filled. This should not be edited.
  • A single blank.
  • The 10-digit last prompt number, right-justified, blank filled.
For example: 
123456789012345678901
         0         98
When modifying the last prompt number, remember that the least significant digit must always be in character position 21. This means that if the current number is "98" and you want to modify it to display "2098" then you must replaces two spaces with the "20", and not just insert the two characters. For example: 
123456789012345678901
         0       2098

Save the file and rerun the submit. No error should be given by conman.