Jes2 - $DO JOBQ,READY

2013-01-07 Thread Tim Brown 
This command recently stopped working eventhough there is output
in the JES2 output that it should display output for. I have an identical
Z/OS system where it does display the output properly.

Thanks,

Tim Brown
Supervisor Computer Operations
Central Hudson Gas & Electric
284 South Ave
Poughkeepsie, NY 12601
Email: tbr...@cenhud.com <>
Phone: 845-486-5643
Fax: 845-486-5921
Cell: 845-235-4255


"This message contains confidential information and is only for the intended 
recipient. If the reader of this message is not the intended recipient, or an 
employee or agent responsible for delivering this message to the intended 
recipient, please notify the sender immediately by replying to this note and 
deleting all copies and attachments."

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Jes2 - $DO JOBQ,READY

2013-01-07 Thread Lizette Koehler 
When you say stop working, I assume you mean it is not selecting work.

Find a job you think should be actioned by the command, then go into SDSF
and issue an I against that job.  See if it matches the criteria for your
command.

Sometimes JES2 will not select work because it does not match the work
selection criteria.  I find the I (INFO) command in SDSF sometimes helpful.

You may not have work that is READY.  It may be held ins some fashion.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf
> Of Tim Brown
> Sent: Monday, January 07, 2013 7:52 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Jes2 - $DO JOBQ,READY
> 
> This command recently stopped working eventhough there is output in the
JES2 output
> that it should display output for. I have an identical Z/OS system where
it does display
> the output properly.
> 
> Thanks,
> 
> Tim Brown
N

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Jes2 - $DO JOBQ,READY

2013-01-07 Thread Tim Brown 
Issuing an "I"  in SDSF NP column gets Invalid command


Thanks,
 
Tim 
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Monday, 07 January, 2013 10:06 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Jes2 - $DO JOBQ,READY

When you say stop working, I assume you mean it is not selecting work.

Find a job you think should be actioned by the command, then go into SDSF and 
issue an I against that job.  See if it matches the criteria for your command.

Sometimes JES2 will not select work because it does not match the work 
selection criteria.  I find the I (INFO) command in SDSF sometimes helpful.

You may not have work that is READY.  It may be held ins some fashion.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On
Behalf
> Of Tim Brown
> Sent: Monday, January 07, 2013 7:52 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Jes2 - $DO JOBQ,READY
> 
> This command recently stopped working eventhough there is output in 
> the
JES2 output
> that it should display output for. I have an identical Z/OS system 
> where
it does display
> the output properly.
> 
> Thanks,
> 
> Tim Brown
N

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Jes2 - $DO JOBQ,READY

2013-01-07 Thread Lizette Koehler 
Tim

What panel were you in when you issued the INFO?  I typically use ST a lot.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf
> Of Tim Brown
> Sent: Monday, January 07, 2013 8:12 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Jes2 - $DO JOBQ,READY
> 
> Issuing an "I"  in SDSF NP column gets Invalid command
> 
> 
> Thanks,
> 
> Tim
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf
> Of Lizette Koehler
> Sent: Monday, 07 January, 2013 10:06 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Jes2 - $DO JOBQ,READY
> 
> When you say stop working, I assume you mean it is not selecting work.
> 
> Find a job you think should be actioned by the command, then go into SDSF
and issue
> an I against that job.  See if it matches the criteria for your command.
> 
> Sometimes JES2 will not select work because it does not match the work
selection
> criteria.  I find the I (INFO) command in SDSF sometimes helpful.
> 
> You may not have work that is READY.  It may be held ins some fashion.
> 
> Lizette
> 
> 
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> > On
> Behalf
> > Of Tim Brown
> > Sent: Monday, January 07, 2013 7:52 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Jes2 - $DO JOBQ,READY
> >
> > This command recently stopped working eventhough there is output in
> > the
> JES2 output
> > that it should display output for. I have an identical Z/OS system
> > where
> it does display
> > the output properly.
> >
> > Thanks,
> >
> > Tim Brown
> N
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Jes2 - $DO JOBQ,READY

2013-01-07 Thread Tim Brown 
All I see once I issue I within ST is,
--
 Job Information  
  
 Job name XTBX290Job class limit exceeded?
 Job ID   JOB00033   Duplicate job name wait? 
 Job schedulable? N/ATime in queue
 Job class mode  Average time in queue
 Job class held? Position in queue of 
 Active jobs in queue 
  
 Scheduling environment   available on these systems: 
  

 And this is the same on both Z/OS systems eventhough $DO JOBQ,READy
on 1 system displays this and 1 doesnt

10.52.13  $HASP686 OUTPUT(XTBX290) 
$HASP686 OUTPUT(XTBX290)   OUTGRP=2.1.1,BURST=NO,FCB=, 
$HASP686   FLASH=,FORMS=STD,HOLD=(NONE),   
$HASP686   OUTDISP=WRITE,PRIORITY=144, 
$HASP686   PRMODE=LINE,QUEUE=4,
$HASP686   RECORDS=(996 OF 996),ROUTECDE=LX290,
$HASP686   SECLABEL=,TPJOBID=,TPJOBN=, 
$HASP686   TSOAVAIL=NO,UCS=,USERID=P08145, 
$HASP686   WRITER= 
  
   
  
  
  
  

Thanks,
 
Tim 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Monday, 07 January, 2013 10:25 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Jes2 - $DO JOBQ,READY

Tim

What panel were you in when you issued the INFO?  I typically use ST a lot.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On
Behalf
> Of Tim Brown
> Sent: Monday, January 07, 2013 8:12 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Jes2 - $DO JOBQ,READY
> 
> Issuing an "I"  in SDSF NP column gets Invalid command
> 
> 
> Thanks,
> 
> Tim
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On
Behalf
> Of Lizette Koehler
> Sent: Monday, 07 January, 2013 10:06 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Jes2 - $DO JOBQ,READY
> 
> When you say stop working, I assume you mean it is not selecting work.
> 
> Find a job you think should be actioned by the command, then go into 
> SDSF
and issue
> an I against that job.  See if it matches the criteria for your command.
> 
> Sometimes JES2 will not select work because it does not match the work
selection
> criteria.  I find the I (INFO) command in SDSF sometimes helpful.
> 
> You may not have work that is READY.  It may be held ins some fashion.
> 
> Lizette
> 
> 
> > -Original Message-
> > From: IBM Mainframe Discussion List 
> > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf
> > Of Tim Brown
> > Sent: Monday, January 07, 2013 7:52 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Jes2 - $DO JOBQ,READY
> >
> > This command recently stopped working eventhough there is output in 
> > the
> JES2 output
> > that it should display output for. I have an identical Z/OS system 
> > where
> it does display
> > the output properly.
> >
> > Thanks,
> >
> > Tim Brown
> N
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email
to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email
to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Jes2 - $DO JOBQ,READY

2013-01-07 Thread Staller, Allan 
What does the system respond with?
Invalid Command, No output?..
What are the console rout codes on the respective images?


All I see once I issue I within ST is,
--
Text deleted   e
 And this is the same on both Z/OS systems eventhough $DO JOBQ,READy on 1 
system displays this and 1 doesnt

10.52.13  $HASP686 OUTPUT(XTBX290) 
$HASP686 OUTPUT(XTBX290)   OUTGRP=2.1.1,BURST=NO,FCB=, 
$HASP686   FLASH=,FORMS=STD,HOLD=(NONE),   
$HASP686   OUTDISP=WRITE,PRIORITY=144, 
$HASP686   PRMODE=LINE,QUEUE=4,
$HASP686   RECORDS=(996 OF 996),ROUTECDE=LX290,
$HASP686   SECLABEL=,TPJOBID=,TPJOBN=, 
$HASP686   TSOAVAIL=NO,UCS=,USERID=P08145, 
$HASP686   WRITER=   

  

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Jes2 - $DO JOBQ,READY

2013-01-07 Thread Lizette Koehler 
Do you have any automation processes on this LPAR that might be interfering
with the JES2 Command?  OPS/MVS Tivoli etc...

If you issue the $DO command do you get any messages?  If so, please provide
the full text with MESSAGE IDs.

Thanks


Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf
> Of Tim Brown
> Sent: Monday, January 07, 2013 9:02 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Jes2 - $DO JOBQ,READY
> 
> All I see once I issue I within ST is,
> --
>  Job Information
> 
>  Job name XTBX290Job class limit exceeded?
>  Job ID   JOB00033   Duplicate job name wait?
>  Job schedulable? N/ATime in queue
>  Job class mode  Average time in queue
>  Job class held? Position in queue of
>  Active jobs in queue
> 
>  Scheduling environment   available on these systems:
> 
> 
>  And this is the same on both Z/OS systems eventhough $DO JOBQ,READy on 1
> system displays this and 1 doesnt
> 
> 10.52.13  $HASP686 OUTPUT(XTBX290)
> $HASP686 OUTPUT(XTBX290)   OUTGRP=2.1.1,BURST=NO,FCB=,
> $HASP686   FLASH=,FORMS=STD,HOLD=(NONE),
> $HASP686   OUTDISP=WRITE,PRIORITY=144,
> $HASP686   PRMODE=LINE,QUEUE=4,
> $HASP686   RECORDS=(996 OF 996),ROUTECDE=LX290,
> $HASP686   SECLABEL=,TPJOBID=,TPJOBN=,
> $HASP686   TSOAVAIL=NO,UCS=,USERID=P08145,
> $HASP686   WRITER=
> 
> 
> 
> 
> 
> 
> 
> Thanks,
> 
> Tim
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf
> Of Lizette Koehler
> Sent: Monday, 07 January, 2013 10:25 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Jes2 - $DO JOBQ,READY
> 
> Tim
> 
> What panel were you in when you issued the INFO?  I typically use ST a
lot.
> 
> Lizette
> 
> 
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> > On
> Behalf
> > Of Tim Brown
> > Sent: Monday, January 07, 2013 8:12 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: Jes2 - $DO JOBQ,READY
> >
> > Issuing an "I"  in SDSF NP column gets Invalid command
> >
> >
> > Thanks,
> >
> > Tim

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Jes2 - $DO JOBQ,READY

2013-01-07 Thread Tim Brown 
Issuing $DO JOBQ on one system displays all jobs where on the other
It displays 

$HASP003 RC=(57),DO JOBQ  - DISPLAY TERMINATED DUE TO EXCESSIVE 
$HASP003OUTPUT (AS DEFINED BY CONDEF DISPMAX)   

Thanks,
 
Tim 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Monday, 07 January, 2013 11:20 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Jes2 - $DO JOBQ,READY

Do you have any automation processes on this LPAR that might be interfering 
with the JES2 Command?  OPS/MVS Tivoli etc...

If you issue the $DO command do you get any messages?  If so, please provide 
the full text with MESSAGE IDs.

Thanks


Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On
Behalf
> Of Tim Brown
> Sent: Monday, January 07, 2013 9:02 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Jes2 - $DO JOBQ,READY
> 
> All I see once I issue I within ST is,
> --
>  Job Information
> 
>  Job name XTBX290Job class limit exceeded?
>  Job ID   JOB00033   Duplicate job name wait?
>  Job schedulable? N/ATime in queue
>  Job class mode  Average time in queue
>  Job class held? Position in queue of
>  Active jobs in queue
> 
>  Scheduling environment   available on these systems:
> 
> 
>  And this is the same on both Z/OS systems eventhough $DO JOBQ,READy 
> on 1 system displays this and 1 doesnt
> 
> 10.52.13  $HASP686 OUTPUT(XTBX290)
> $HASP686 OUTPUT(XTBX290)   OUTGRP=2.1.1,BURST=NO,FCB=,
> $HASP686   FLASH=,FORMS=STD,HOLD=(NONE),
> $HASP686   OUTDISP=WRITE,PRIORITY=144,
> $HASP686   PRMODE=LINE,QUEUE=4,
> $HASP686   RECORDS=(996 OF 996),ROUTECDE=LX290,
> $HASP686   SECLABEL=,TPJOBID=,TPJOBN=,
> $HASP686   TSOAVAIL=NO,UCS=,USERID=P08145,
> $HASP686   WRITER=
> 
> 
> 
> 
> 
> 
> 
> Thanks,
> 
> Tim
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On
Behalf
> Of Lizette Koehler
> Sent: Monday, 07 January, 2013 10:25 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Jes2 - $DO JOBQ,READY
> 
> Tim
> 
> What panel were you in when you issued the INFO?  I typically use ST a
lot.
> 
> Lizette
> 
> 
> > -Original Message-
> > From: IBM Mainframe Discussion List 
> > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf
> > Of Tim Brown
> > Sent: Monday, January 07, 2013 8:12 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: Jes2 - $DO JOBQ,READY
> >
> > Issuing an "I"  in SDSF NP column gets Invalid command
> >
> >
> > Thanks,
> >
> > Tim

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Jes2 - $DO JOBQ,READY

2013-01-07 Thread Lizette Koehler 
Tim,

You can temporarily raise the CONDEF DISPMAX to a higher number to get all
the output.  Otherwise, the command worked but it could not display
everything on the queue.
Look up the $T CONDEF command


Lizette

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf
> Of Tim Brown
> Sent: Monday, January 07, 2013 9:24 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Jes2 - $DO JOBQ,READY
> 
> Issuing $DO JOBQ on one system displays all jobs where on the other It
displays
> 
> $HASP003 RC=(57),DO JOBQ  - DISPLAY TERMINATED DUE TO EXCESSIVE
> $HASP003OUTPUT (AS DEFINED BY CONDEF DISPMAX)
> 
> Thanks,
> 
> Tim
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf
> Of Lizette Koehler
> Sent: Monday, 07 January, 2013 11:20 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Jes2 - $DO JOBQ,READY
> 
> Do you have any automation processes on this LPAR that might be
interfering with the
> JES2 Command?  OPS/MVS Tivoli etc...
> 
> If you issue the $DO command do you get any messages?  If so, please
provide the
> full text with MESSAGE IDs.
> 
> Thanks
> 
> 
> Lizette
> 
> 
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> > On
> Behalf
> > Of Tim Brown
> > Sent: Monday, January 07, 2013 9:02 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: Jes2 - $DO JOBQ,READY
> >
> > All I see once I issue I within ST is,
> >
--
> >  Job Information
> >
> >  Job name XTBX290Job class limit exceeded?
> >  Job ID   JOB00033   Duplicate job name wait?
> >  Job schedulable? N/ATime in queue
> >  Job class mode  Average time in queue
> >  Job class held? Position in queue of
> >  Active jobs in queue
> >
> >  Scheduling environment   available on these systems:
> >
> >
> >  And this is the same on both Z/OS systems eventhough $DO JOBQ,READy
> > on 1 system displays this and 1 doesnt
> >
> > 10.52.13  $HASP686 OUTPUT(XTBX290)
> > $HASP686 OUTPUT(XTBX290)   OUTGRP=2.1.1,BURST=NO,FCB=,
> > $HASP686   FLASH=,FORMS=STD,HOLD=(NONE),
> > $HASP686   OUTDISP=WRITE,PRIORITY=144,
> > $HASP686   PRMODE=LINE,QUEUE=4,
> > $HASP686   RECORDS=(996 OF 996),ROUTECDE=LX290,
> > $HASP686   SECLABEL=,TPJOBID=,TPJOBN=,
> > $HASP686   TSOAVAIL=NO,UCS=,USERID=P08145,
> > $HASP686   WRITER=
> >
> >
> >
> >
> >
> >
> >
> > Thanks,
> >
> > Tim
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> > On
> Behalf
> > Of Lizette Koehler
> > Sent: Monday, 07 January, 2013 10:25 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: Jes2 - $DO JOBQ,READY
> >
> > Tim
> >
> > What panel were you in when you issued the INFO?  I typically use ST a
> lot.
> >
> > Lizette
> >
> >
> > > -Original Message-
> > > From: IBM Mainframe Discussion List
> > > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> > Behalf
> > > Of Tim Brown
> > > Sent: Monday, January 07, 2013 8:12 AM
> > > To: IBM-MAIN@LISTSERV.UA.EDU
> > > Subject: Re: Jes2 - $DO JOBQ,READY
> > >
> > > Issuing an "I"  in SDSF NP column gets Invalid command
> > >
> > >
> > > Thanks,
> > >
> > > Tim

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Jes2 - $DO JOBQ,READY

2013-01-07 Thread Tim Brown 
Its our automation software, when I ended  it I got the results  of - $DO 
JOBQ,READY
and when I restarted it I didn't

Need to review what changed within that product

Thanks!!!
 
Tim 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Monday, 07 January, 2013 11:34 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Jes2 - $DO JOBQ,READY

Tim,

You can temporarily raise the CONDEF DISPMAX to a higher number to get all the 
output.  Otherwise, the command worked but it could not display everything on 
the queue.
Look up the $T CONDEF command


Lizette

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On
Behalf
> Of Tim Brown
> Sent: Monday, January 07, 2013 9:24 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Jes2 - $DO JOBQ,READY
> 
> Issuing $DO JOBQ on one system displays all jobs where on the other It
displays
> 
> $HASP003 RC=(57),DO JOBQ  - DISPLAY TERMINATED DUE TO EXCESSIVE
> $HASP003OUTPUT (AS DEFINED BY CONDEF DISPMAX)
> 
> Thanks,
> 
> Tim
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On
Behalf
> Of Lizette Koehler
> Sent: Monday, 07 January, 2013 11:20 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Jes2 - $DO JOBQ,READY
> 
> Do you have any automation processes on this LPAR that might be
interfering with the
> JES2 Command?  OPS/MVS Tivoli etc...
> 
> If you issue the $DO command do you get any messages?  If so, please
provide the
> full text with MESSAGE IDs.
> 
> Thanks
> 
> 
> Lizette
> 
> 
> > -Original Message-
> > From: IBM Mainframe Discussion List 
> > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf
> > Of Tim Brown
> > Sent: Monday, January 07, 2013 9:02 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: Jes2 - $DO JOBQ,READY
> >
> > All I see once I issue I within ST is,
> >
--
> >  Job Information
> >
> >  Job name XTBX290Job class limit exceeded?
> >  Job ID   JOB00033   Duplicate job name wait?
> >  Job schedulable? N/ATime in queue
> >  Job class mode  Average time in queue
> >  Job class held? Position in queue of
> >  Active jobs in queue
> >
> >  Scheduling environment   available on these systems:
> >
> >
> >  And this is the same on both Z/OS systems eventhough $DO JOBQ,READy 
> > on 1 system displays this and 1 doesnt
> >
> > 10.52.13  $HASP686 OUTPUT(XTBX290)
> > $HASP686 OUTPUT(XTBX290)   OUTGRP=2.1.1,BURST=NO,FCB=,
> > $HASP686   FLASH=,FORMS=STD,HOLD=(NONE),
> > $HASP686   OUTDISP=WRITE,PRIORITY=144,
> > $HASP686   PRMODE=LINE,QUEUE=4,
> > $HASP686   RECORDS=(996 OF 996),ROUTECDE=LX290,
> > $HASP686   SECLABEL=,TPJOBID=,TPJOBN=,
> > $HASP686   TSOAVAIL=NO,UCS=,USERID=P08145,
> > $HASP686       WRITER=
> >
> >
> >
> >
> >
> >
> >
> > Thanks,
> >
> > Tim
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List 
> > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf
> > Of Lizette Koehler
> > Sent: Monday, 07 January, 2013 10:25 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: Jes2 - $DO JOBQ,READY
> >
> > Tim
> >
> > What panel were you in when you issued the INFO?  I typically use ST 
> > a
> lot.
> >
> > Lizette
> >
> >
> > > -Original Message-
> > > From: IBM Mainframe Discussion List 
> > > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> > Behalf
> > > Of Tim Brown
> > > Sent: Monday, January 07, 2013 8:12 AM
> > > To: IBM-MAIN@LISTSERV.UA.EDU
> > > Subject: Re: Jes2 - $DO JOBQ,READY
> > >
> > > Issuing an "I"  in SDSF NP column gets Invalid command
> > >
> > >
> > > Thanks,
> > >
> > > Tim

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Jes2 - $DO JOBQ,READY

2013-01-07 Thread Mark Zelden 
On Mon, 7 Jan 2013 09:34:06 -0700, Lizette Koehler  
wrote:

>Tim,
>
>You can temporarily raise the CONDEF DISPMAX to a higher number to get all
>the output.  Otherwise, the command worked but it could not display
>everything on the queue.
>Look up the $T CONDEF command
>
>

An easier way without changing anything is to add ",L=Z" to the command.

$DO JOBQ,L=Z

--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS   
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html 
Systems Programming expert at http://expertanswercenter.techtarget.com/

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN