|
View previous topic :: View next topic
|
| Author |
Message |
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
I can't agree that there is no other option. There are job schedulers which provide this sort of functionality. Also, why can't the user who's submitting the job (using the REXX) use SDSF to see the job complete and examine the cond codes? Properly implemented security around SDSF can be used to limit a user's SDSF access.
The submitted job will use the same amount of resources (CPU &c.) whether or not you use this option.
Using this option could result in huge increases in resource usage which, in turn, could lead to disciplinary action - possible even job loss. Even if you intend only one or two users to have access to this, these things have a tendency to creep into general usage.
Garry. |
|
| Back to top |
|
 |
sakrat
Active User
Joined: 05 Feb 2014
Posts: 164
Location: India
|
|
|
|
| Garry Carroll wrote: |
I can't agree that there is no other option. There are job schedulers which provide this sort of functionality. Also, why can't the user who's submitting the job (using the REXX) use SDSF to see the job complete and examine the cond codes? Properly implemented security around SDSF can be used to limit a user's SDSF access.
The submitted job will use the same amount of resources (CPU &c.) whether or not you use this option.
Using this option could result in huge increases in resource usage which, in turn, could lead to disciplinary action - possible even job loss. Even if you intend only one or two users to have access to this, these things have a tendency to creep into general usage.
Garry. |
Now I feel like you are right. What I thought was automating everything with just user entering only 3 fields. From which the job is submitted and a report is created. So that if the RC is zero using that report's data new file is created in comma separated format by finding whether the job name is present in that report and details of those jobname from that report is taken moved to the new file and is sent mail. Its basically like creating the control m doc.
But I dint think of the cpu resources usage that happens to be high when automating the the job run through rexx. |
|
| Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
While I'm not fully aware of what you're trying to achieve, perhaps what you want to do is modify the submitted job to add a sort (DFSORT or SYNCSORT) step to produce the .csv file from the report created if the cond code from the report step is zero. Also add another step, again based on cond code zero, to send the e-mail using the z/OS SMTP server?
Is that an option?
Garry. |
|
| Back to top |
|
|
sakrat
Active User
Joined: 05 Feb 2014
Posts: 164
Location: India
|
|
|
|
No actually my idea for creating the rexx tool is to automate the process of creating the control m document which will be used as part of release documentation.
So what I thought was create a panel where user will input the change man package name where the jcls reside, scheduler names that which will be used for creating the report.
Once the user inputs the detail, next ispf table will be opened in the panel containing the jcl names that is taken from package. Now the user will select the jobs that is needed in document and press enter.
Next in the the background the job will be submitted where a readable format of the control m table specified by the user will be created from the job.
It checks for RC of the job submitted to make sure report is created.
Now the jcl names which the user selected from the ispf table will be founf one by one in the report and the details corresponding to the jcl will be moved to sstem variable and written into new file with comma separated.
Once all the jcls are found and written into the new file, it will be sent to the specific mail with csv format excel sheet. So that now the control m doc is created. |
|
| Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
Assuming that you can get everything done up to the point of produucing the report, continue from....
| Quote: |
It checks for RC of the job submitted to make sure report is created.
Now the jcl names which the user selected from the ispf table will be founf one by one in the report and the details corresponding to the jcl will be moved to sstem variable and written into new file with comma separated.
Once all the jcls are found and written into the new file, it will be sent to the specific mail with csv format excel sheet. So that now the control m doc is created. |
If your REXX builds the necessary DFSORT/SYNCSORT control cards to identify the 'jcl names' (jobnames?) that the user entered, the necessary control cards can be built by the REXX to be used in a sort step to extract the details from the report into a comma separated file. This comma separated file can be attached in MIME format to an email to be sent by z/OS SMTP server to whatever email address you (or the users) specify. This can all be achieved within the submitted job.
Garry. |
|
| Back to top |
|
|
sakrat
Active User
Joined: 05 Feb 2014
Posts: 164
Location: India
|
|
|
|
| Garry Carroll wrote: |
Assuming that you can get everything done up to the point of produucing the report, continue from....
| Quote: |
It checks for RC of the job submitted to make sure report is created.
Now the jcl names which the user selected from the ispf table will be founf one by one in the report and the details corresponding to the jcl will be moved to sstem variable and written into new file with comma separated.
Once all the jcls are found and written into the new file, it will be sent to the specific mail with csv format excel sheet. So that now the control m doc is created. |
If your REXX builds the necessary DFSORT/SYNCSORT control cards to identify the 'jcl names' (jobnames?) that the user entered, the necessary control cards can be built by the REXX to be used in a sort step to extract the details from the report into a comma separated file. This comma separated file can be attached in MIME format to an email to be sent by z/OS SMTP server to whatever email address you (or the users) specify. This can all be achieved within the submitted job.
Garry. |
you mean to add one more step in the job which is submitted for created the report and other for sending the mail... right...? |
|
| Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
Yes, one more step to process the report and produce the .csv file and another step after that to send the mail with .csv file as an attachment.
Garry. |
|
| Back to top |
|
|
sakrat
Active User
Joined: 05 Feb 2014
Posts: 164
Location: India
|
|
|
|
| Garry Carroll wrote: |
Yes, one more step to process the report and produce the .csv file and another step after that to send the mail with .csv file as an attachment.
Garry. |
Ok will try it out and then let you know. ... anyway thanks for helping me.. I learned a new concept sdsf in rexx and how can we use it... this topic was new learning to me.....  |
|
| Back to top |
|
|
|
|
