RE: STRSRVJOB problems

["Dave Murvin" <Dave.Murvin@xxxxxxxxxxxxxxxxx>]

Thanks.  I am embarrassed that this must have been the cause.  When I
came into work today and started all new sessions. I did not have the
problem.  I get a lot of multi-tasking/interruptions and I work with
multiple sessions on each machine and must of "forgot" what I that I had
debug going on one of the sessions. I would normally pick up on this
cause when using the debug command, but I did not think of it on the
STRSRVJOB command.  Anyway, I hope that sounds good as an excuse.  :)

Dave

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, April 02, 2008 8:23 PM
To: Midrange Systems Technical Discussion
Subject: Re: STRSRVJOB problems

I did a DSPMSGD CPD0039 (thank you, that's a big help). 
Cause . . . . . :   The command is not valid in the current mode of 
operation.
  The possible modes are production, debug, or service. The Display 
Command 
  (DSPCMD) command can be used to determine the modes in which the
command 
is 
  allowed.  
Recovery  . . . :   Omit the command or enter a proper mode: production

  (ENDDBG or ENDSRVJOB command), debug (STRDBG command), or service 
(STRSRVJOB
  command).  

I know you're pretty sure that you weren't already in STRDBG OR
STRSRVJOB 
but try the appropriate END... commands and see if they tell you to
FOAD.

Rob Berendt