IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

REXX to print ST screen (SDSF) to a dataset


IBM Mainframe Forums -> CLIST & REXX
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Ramanan-R

New User


Joined: 21 Mar 2007
Posts: 66
Location: Chennai, Tamilnadu, India

PostPosted: Tue Dec 02, 2008 8:02 pm
Reply with quote

Hi All icon_smile.gif,

I searched the forum for the following requirement, but couldn't succeed.

For a particular owner and prefix, i want to print the ST screen (SDSF) to a sequential dataset, which i'll use as an input to run an exec.

Thanks!

Regards,
Ramanan R
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Tue Dec 02, 2008 9:24 pm
Reply with quote

How do you want to print it, from an online session, or perhaps a batch job.

SDSF & XDC have been rather discussed to death in the forum, so given a little hint of those keywords, maybe another search may provle a smidge more fruitful.
Back to top
View user's profile Send private message
Ramanan-R

New User


Joined: 21 Mar 2007
Posts: 66
Location: Chennai, Tamilnadu, India

PostPosted: Wed Dec 03, 2008 6:52 am
Reply with quote

Hi Expat,

Thanks for your reply. I want to take a print of ST screen for batch jobs.

I tried different search terms to find how to print the screen but couldn't get thru, hence started this topic.

All topic deals with how to take joblog to PDS/PS thru REXX, JCL etc but not dealing with screen printing...

Regards,
Ramanan R
Back to top
View user's profile Send private message
ofer71

Global Moderator


Joined: 27 Dec 2005
Posts: 2358
Location: Israel

PostPosted: Wed Dec 03, 2008 11:44 am
Reply with quote

Search the forum for "batch SDSF".

O.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Wed Dec 03, 2008 10:20 pm
Reply with quote

Hello,

Quote:
but not dealing with screen printing...
You will not be "screen printing". You would use batch sdsf to gather the info you want and write the info you want to a dataset (in the format you want as opposed to some screen image).
Back to top
View user's profile Send private message
ganeshprasanna

New User


Joined: 21 Feb 2009
Posts: 36
Location: South Portland, Maine

PostPosted: Mon Mar 02, 2009 8:38 pm
Reply with quote

Hello,

Any luck on this?
I tried hard on this the whole weekend.But no luck.
I am able to print job details for a job such as SYSOUT etc into a file, wheres unable to print the complete list of jobs for certain filter or sorting.

I mean for example:
ST
OWNER Mxxxxxx

Now i need to extract these set of jobs into a file.
Any help on this would be appreciated.

Thanks
Back to top
View user's profile Send private message
zhanghz

New User


Joined: 15 Oct 2008
Posts: 6
Location: Singapore

PostPosted: Tue Mar 03, 2009 4:21 pm
Reply with quote

SDSF batch, refer to manual "SDSF Operation and Customization" chapter 11.

It prints the whole screen. You can see the screens in output "ISFOUT". You may want to use PGM=ISFAFD and do AFD REFRESH before printing to force refreshing the SDSF screen.

You can print the complete list in the screen, refer to chapter 11.
Back to top
View user's profile Send private message
ganeshprasanna

New User


Joined: 21 Feb 2009
Posts: 36
Location: South Portland, Maine

PostPosted: Tue Mar 03, 2009 9:21 pm
Reply with quote

Hi ,

I tried this


QUEUE "PRE MITGMK*" /* SDSF COMMANDS IN BATCH*/
QUEUE "OWNER MITGMK*"
QUEUE "ST"
QUEUE "PRINT FILE TEMPPRT" /* PRINT TO TEMP DATASET */
QUEUE "PRINT 1 999999"
QUEUE "PRINT CLOSE"
QUEUE "END"
QUEUE "EXIT"

but below code worked fine..
QUEUE "PRE MITGMK*" /* SDSF COMMANDS IN BATCH*/
QUEUE "OWNER MITGMK*"
QUEUE "ST"
QUEUE "FILTER JOBNAME " JOBID
QUEUE "FIND JOBNAME"
++S
QUEUE "PRINT FILE TEMPPRT" /* PRINT TO TEMP DATASET */
QUEUE "PRINT 1 999999"
QUEUE "PRINT CLOSE"
QUEUE "END"
QUEUE "EXIT"


Can you tell me what is my mistake? i am not able to figure out.
Back to top
View user's profile Send private message
ofer71

Global Moderator


Joined: 27 Dec 2005
Posts: 2358
Location: Israel

PostPosted: Tue Mar 03, 2009 9:56 pm
Reply with quote

Have you pre-allocated TEMPPRT?

O.
Back to top
View user's profile Send private message
Pedro

Global Moderator


Joined: 01 Sep 2006
Posts: 2546
Location: Silicon Valley

PostPosted: Wed Mar 04, 2009 2:55 am
Reply with quote

For the example that you want and that does not work, what are the final contents of TEMPPRT and ISFOUT?
Back to top
View user's profile Send private message
ganeshprasanna

New User


Joined: 21 Feb 2009
Posts: 36
Location: South Portland, Maine

PostPosted: Wed Mar 04, 2009 6:44 am
Reply with quote

TEMPPRT is preallocated. But an empty file is created in this case.

ISFOUT contents:

there is an error in this statement shown:

PRINT 1 999999
- Invalid parm

Not sure about the error.I check the syntax. It seems to be fine.

I tried the same from the usual SDSF panel by giving one command at a time.

OWNER MITGMK
ST
PRINT ODSN 'MY DATA SET'
PRINT 1 999999 - invalid parm
PRINT CLOSE
Back to top
View user's profile Send private message
gcicchet

Senior Member


Joined: 28 Jul 2006
Posts: 1702
Location: Australia

PostPosted: Wed Mar 04, 2009 7:18 am
Reply with quote

Hi,

if you try PRINT 1 999 what happens ?


Gerry
Back to top
View user's profile Send private message
ganeshprasanna

New User


Joined: 21 Feb 2009
Posts: 36
Location: South Portland, Maine

PostPosted: Wed Mar 04, 2009 8:37 am
Reply with quote

Executed following commands
Open SDSF panel
ST
PRINT ODSN "DATASET NAME" (This is already created before hand)
PRINT 1 999

Here is what i get below:

Code:
SDSF STATUS DISPLAY ALL CLASSES                               PARM INVALID 
COMMAND INPUT ===> PRINT 1 999                                SCROLL ===> CSR
PREFIX=*  DEST=(ALL)  OWNER=MITGMK  SORT=Pos/A  SYSNAME=                     


I get the same response. PARM INVALID.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Wed Mar 04, 2009 9:38 am
Reply with quote

Hello,

Try using PRINT only (after issuing the PRINT ODSN. . .).
Back to top
View user's profile Send private message
ganeshprasanna

New User


Joined: 21 Feb 2009
Posts: 36
Location: South Portland, Maine

PostPosted: Wed Mar 04, 2009 5:12 pm
Reply with quote

Open SDSF panel
ST
PRINT ODSN 'Dataset name'
PRINT
PRINT CLOSE

No error in syntax.
Nothing is saved in the dataset.

Final output on spool after PRINT CLOSE

SDSF STATUS DISPLAY ALL CLASSES PRINT CLOSED 0 LINE
COMMAND INPUT ===> SCROLL ===> CSR

Still not working as desired. cant we take a print of list of jobs running in the spool? i guess this is possible right?
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Wed Mar 04, 2009 5:16 pm
Reply with quote

Quote:
TEMPPRT is preallocated. But an empty file is created in this case.

By preallocated, do you mean it is allocated in the same step, or in a previous step.

I can recall getting the same problem a few years back when the output was allocated in the same jobstep, but everything worked fine if the dataset was created in a previous job step.
Back to top
View user's profile Send private message
ganeshprasanna

New User


Joined: 21 Feb 2009
Posts: 36
Location: South Portland, Maine

PostPosted: Wed Mar 04, 2009 5:28 pm
Reply with quote

Dataset was allocated in the previous step.

It worked fine for me too only for the condition wherein i want to get details of a particular job using

FIND JOBNAME
++S


> But if i want to print the spool listing which is

ST
OWNER ABCDEF

now print..

PRINT ODSN "dataset"
PRINT 1 99999
PRINT CLOSE

I get syntax error:
PRINT 1 99999 PARM INVALID
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Wed Mar 04, 2009 6:03 pm
Reply with quote

OK, having read your thread again, I think that you will find that screen type prints will be output to the DDname ISFOUT regardless of where you want then to go.
Code:

//SDSF     EXEC PGM=SDSF,PARM='++725,133'   
//SYSOUT   DD SYSOUT=*                     
//SYSPRINT DD SYSOUT=*                     
//ISFOUT   DD SYSOUT=*                     
//ISFIN    DD *                             
PRE *                                       
DA OJOB                                     
SORT JOBNAME/A                             
END                                         
EXIT                                       

Gives me what I want, unfortunately with a load of other SDSF pages which I have had to filter out with some REXX code.
Back to top
View user's profile Send private message
zhanghz

New User


Joined: 15 Oct 2008
Posts: 6
Location: Singapore

PostPosted: Thu Mar 05, 2009 6:27 am
Reply with quote

seems we can't use PRINT on the list of jobs in SDSF screens.

you can use SDSF batch to print full screens and go through the screen and filter out the jobs.

//SDSFBAT EXEC PGM=ISFAFD
//ISFOUT DD SYSOUT=*
//ISFIN DD *
PRE MYJOB*
ST
SORT JOBNAME A
AFD REFRESH
++ALL
//*

The series of screens are in ISFOUT.
Back to top
View user's profile Send private message
zhanghz

New User


Joined: 15 Oct 2008
Posts: 6
Location: Singapore

PostPosted: Thu Mar 05, 2009 6:33 am
Reply with quote

Oops, didn't see expat's post above...
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> CLIST & REXX

 


Similar Topics
Topic Forum Replies
No new posts Running REXX through JOB CLIST & REXX 13
No new posts Error to read log with rexx CLIST & REXX 11
No new posts isfline didnt work in rexx at z/OS ve... CLIST & REXX 7
No new posts run rexx code with jcl CLIST & REXX 15
No new posts Execute secondary panel of sdsf with ... CLIST & REXX 1
Search our Forums:

Back to Top