Re: Debugging a batch job

When I try to do the traditional STRSRVJOB/STRDBG on this job it brings up
the source but when I try to set a breakpoint I get:
Message ID . . . . . . :   CPF1938
Date sent  . . . . . . :   11/07/01      Time sent  . . . . . . :
08:43:10
Message . . . . :   Command is not allowed while serviced job is not
active.
Cause . . . . . :   You tried to enter a debug command to a serviced job,
but
  that job is not active.  The job was not active for one of the following
  reasons:
    -- The job was held on the job queue because the Hold Job (HLDJOB)
command
  or the Hold Job Queue (HLDJOBQ) command was used.
    -- The job was held after it started running because the Hold Job
(HLDJOB)
  command was used.
    -- The job stopped processing temporarily because the Transfer
Secondary
  Job (TFRSECJOB) command or the Transfer Group Job (TFRGRPJOB) command was
  used.
Recovery  . . . :   Do one of the following and try the request again:
    -- If The job was held on the job queue, use the Release Job (RLSJOB)
  command to release the job or use the Release Job Queue (RLSJOBQ) command
to
  release the job queue.
    -- If the job was held after it started running, use the Release Job
  (RLSJOB) command to release the job.
    -- If the job stopped processing temporarily because the Transfer
  Secondary Job (TFRSECJOB) command or the Transfer Group Job (TFRGRPJOB)
  command was used, transfer back to the alternative job using the System
  Request menu or transfer back to the group job using the Transfer Group
Job
  (TFRGRPJOB) command.
Technical description . . . . . . . . :   In order for the debug command to
  complete, data must be processed by the serviced job.  However, the job
is
  not active, so the job cannot run to process the data.


Rob Berendt

==================
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin