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

REXX - CLIST program to be invoked after batch job is over


IBM Mainframe Forums -> CLIST & REXX
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
pkmurali
Warnings : 1

Active User


Joined: 15 Dec 2005
Posts: 271

PostPosted: Wed Sep 04, 2019 4:31 pm
Reply with quote

Hi All,

I have to copy a large dataset ( of volume 1.9 million records) with LRECL 141 with Blocksize 27918 to LRECRL 80 and BLKSIZE 800. This helps me to view the dataset and macro can be applied. Right now I am submitting a jcl to convert the file into viewable format. then I am executing the macro through panels. I wish to invoke the batch job through rexx-clist and once the job completes and output dataset is created then the macro needs to be invoked (handshake). Is there anyway in REXX to make the program in wait and invoked when batch job is completed. I agree we can trigger the rexx program in next step of the batch job. But I wish to know if there is any other possibilities.

Thanks,
Murali.
Back to top
View user's profile Send private message
sergeyken

Senior Member


Joined: 29 Apr 2008
Posts: 2019
Location: USA

PostPosted: Wed Sep 04, 2019 4:59 pm
Reply with quote

pkmurali wrote:
Hi All,

I have to copy a large dataset ( of volume 1.9 million records) with LRECL 141 with Blocksize 27918 to LRECRL 80 and BLKSIZE 800. This helps me to view the dataset and macro can be applied. Right now I am submitting a jcl to convert the file into viewable format. then I am executing the macro through panels. I wish to invoke the batch job through rexx-clist and once the job completes and output dataset is created then the macro needs to be invoked (handshake). Is there anyway in REXX to make the program in wait and invoked when batch job is completed. I agree we can trigger the rexx program in next step of the batch job. But I wish to know if there is any other possibilities.

Thanks,
Murali.

1) Any file viewability has nothing to do with its LRECL, and furthermore its BLKSIZE. There is absolutely no need to convert the dataset for this purpose, and in this manner.

2) LRECL=141 cannot be physically converted to LRECL=80 without truncation (e.g. elimination) of part of its data.

3) It is unclear the proposed role of any REXX/CLIST, and/or any MACRO just to view the file? There are plenty of tools supposed to support various files viewing.

4) The size of 1.4M records isn't a huge file in modern world. Big files start from at least 100M rows, often much bigger.
Back to top
View user's profile Send private message
Rohit Umarjikar

Global Moderator


Joined: 21 Sep 2010
Posts: 3051
Location: NYC,USA

PostPosted: Wed Sep 04, 2019 5:06 pm
Reply with quote

In a REXX you can check if the Data set is created and available and if not then send an error to retry after sometime.

Even if it’s possible, you are locking the TSO Session for infinite time, not a good idea at all. It’s not a CICS.
Back to top
View user's profile Send private message
Nic Clouston

Global Moderator


Joined: 10 May 2007
Posts: 2455
Location: Hampshire, UK

PostPosted: Wed Sep 04, 2019 6:31 pm
Reply with quote

Why do you want such an inefficient block size? What is wrong with using 1/2 track blocking - nowadays BLKSIZE=0?
Back to top
View user's profile Send private message
sergeyken

Senior Member


Joined: 29 Apr 2008
Posts: 2019
Location: USA

PostPosted: Wed Sep 04, 2019 9:25 pm
Reply with quote

pkmurali wrote:
Right now I am submitting a jcl to convert the file into viewable format. then I am executing the macro through panels. I wish to invoke the batch job through rexx-clist and once the job completes and output dataset is created then the macro needs to be invoked (handshake). Is there anyway in REXX to make the program in wait and invoked when batch job is completed.

There is no doubt that it is not JCL which performs any file conversion (something extra, except LRECL=141 to LRECL=80, I hope?). One can be sure there must be a program (a load module, or REXX script, or whatever else) invoked by this JCL; it is the thing which actually performs this "conversion".
JCL is not able to perform any conversion by itself, ever!

If so, there should be no problem just to call exactly the same program (load module, REXX script, or whatever else) right from your initially mentioned REXX, without involving absolutely unneeded JCL into this, so to speak, "process".
Back to top
View user's profile Send private message
steve-myers

Active Member


Joined: 30 Nov 2013
Posts: 917
Location: The Universe

PostPosted: Wed Sep 04, 2019 10:21 pm
Reply with quote

pkmurali wrote:
Hi All,

I have to copy a large dataset ( of volume 1.9 million records) with LRECL 141 with Blocksize 27918 to LRECRL 80 and BLKSIZE 800. This helps me to view the dataset and macro can be applied. Right now I am submitting a jcl to convert the file into viewable format. then I am executing the macro through panels. I wish to invoke the batch job through rexx-clist and once the job completes and output dataset is created then the macro needs to be invoked (handshake). Is there anyway in REXX to make the program in wait and invoked when batch job is completed. I agree we can trigger the rexx program in next step of the batch job. But I wish to know if there is any other possibilities.

Thanks,
Murali.

  • You can browse a data set with any RECFM and LRECL. There is no need to copy the data set with LRECL=80. ISPF "browse" is not ISPF "view," though only us (mostly retired now) dinosaurs really appreciate the difference. Sadly, the default in ISPF is "view" rather than "browse," but that is easy to change.
  • As others have noted, a large data set with LRECL=80, BLKSIZE=800 is very inefficient in space usage. In traditional rotating DASD a data set with those attributes is quite slow, but in modern DASD it's not quite so bad. One of these days I will rant on about why this is true, but not in this topic or this forum.
  • As others have noted, it's not really a good idea to let your TSO session to just wait for a longer running batch job to end, even if there was an API to allow a Rexx EXEC to simply wait for a job to end.
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 Compile Several JCL JOB Through one r... CLIST & REXX 4
No new posts Using API Gateway from CICS program CICS 0
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
Search our Forums:

Back to Top