Page 2 of 2

Re: Automation Tool

PostPosted: Wed Nov 03, 2010 2:12 pm
by shamaam2
prino wrote:
  1. Compile one PL/I program and one CICS program using your site's standard procedures.
  2. Save both sets of JCL, for example via the SJ line command in SDSF
  3. Replace every occurrence of the program being compiled in the save JCL with &THISPGM and add a single
    //   SET THISPGM='WHATEVER'
    statement to the JCL
  4. Create two edit macro's like these, one for the BATCH program and one for the CICS ones, suggest to call them SUBBATCH and SUBCICS
    /* REXX */
    "isredit macro"
    pgm.1 = 'WHATEVER'
    pgm.2 = 'AAAA'
    pgm.3 = 'AAAB'
    .
    .
    .
    pgm.198 = 'ZWER'
    pgm.0 = 198

    do i = 2 to pgm.0
      j = i - 1
      "isredit c '"pgm.j"' '"pgm.i"' first"
      "isredit submit"
    end

    i = pgm.0
    "isredit c '"pgm.i'" '"pgm.1"' first"
  5. Go into the member containing the BATCH compile JCL and enter SUBBATCH
  6. Go into the member containing the BATCH compile JCL and enter SUBCICS

Macro written on the fly, untested



Thanks prino. will try it... :-)

Re: Automation Tool

PostPosted: Wed Nov 03, 2010 2:20 pm
by enrico-sorichetti
my post was written in plain english , not sms droid style like Yours
so You should not have any issues in understanding it

it was not me who was claiming lack of time ...
a poor planning of the task - inadequate time/skills
is not a reason to have responders do the work You are getting paid for

furthermore if You are in a provider/customer relation it would be better
to review Your organization skills map ...
Your organization is selling competences that it does not have

what is wrong in following the advice given...
work with Your support to create the procedures for compile/builds/<call it any name You want>
thats the first step anyway which is done when a new application is being developed
create the standards and all the utility procedures

and then ...
//<jobname> JOB ... job related info ...
//<step1> EXEC <theproc>,THING=<the name of Your thing>
//...
//<stepn> EXEC <theproc>,THING=<the name of Your last thing>

nothing that a decent support people should not be able to do

for all You might want to know about IBM documentation
http://www-03.ibm.com/systems/z/os/zos/ ... index.html

Re: Automation Tool

PostPosted: Wed Nov 03, 2010 2:44 pm
by shamaam2
enrico-sorichetti wrote:my post was written in plain english , not sms droid style like Yours
so You should not have any issues in understanding it

it was not me who was claiming lack of time ...
a poor planning of the task - inadequate time/skills
is not a reason to have responders do the work You are getting paid for

furthermore if You are in a provider/customer relation it would be better
to review Your organization skills map ...
Your organization is selling competences that it does not have

what is wrong in following the advice given...
work with Your support to create the procedures for compile/builds/<call it any name You want>
thats the first step anyway which is done when a new application is being developed
create the standards and all the utility procedures

and then ...
//<jobname> JOB ... job related info ...
//<step1> EXEC <theproc>,THING=<the name of Your thing>
//...
//<stepn> EXEC <theproc>,THING=<the name of Your last thing>

nothing that a decent support people should not be able to do

for all You might want to know about IBM documentation
http://www-03.ibm.com/systems/z/os/zos/ ... index.html



I understand... Thanks....

I take up your advice and plan things accordingly hereafter. and Not simply NOD head for whatever they say....

Re: Automation Tool

PostPosted: Wed Nov 03, 2010 5:16 pm
by NicC
and Not simply NOD head for whatever they say

and good luck to you.
By the way, Prino's post contains an error. This line:
6. Go into the member containing the BATCH compile JCL and enter SUBCICS

should say:
6. Go into the member containing the CICS compile JCL and enter SUBCICS