ESP Workload Automation

 View Only
  • 1.  test runs with CA7 r12 questions

    Posted Feb 12, 2016 01:25 PM

    I am testing running batches with our CA7 r12.  We have the entire database on the new release.   I am having to put a hold on the scheduler so that jobs that would normally be scheduled don't try to run on the test ca7.  But when we ran one of the test batches last night, ALL the jobs came in on hold and I had to release the hold on each job as it came into the queue.   Is there a way that I can make triggered jobs not have a hold on them but still make it so that scheduled jobs never come into the queue?

     

    renate



  • 2.  Re: test runs with CA7 r12 questions
    Best Answer

    Posted Feb 16, 2016 04:35 PM

    You can start 7 with schedule scan turned off by changing the INIT statement to have RUNOPT=NSTA (instead of RUNOPT=SCAN).  This way no jobs enter the queue via schedule scan, but you can DEMAND work and have it trigger--long story short--there is no way to have scanned jobs on hold but triggers not.



  • 3.  Re: test runs with CA7 r12 questions

    Posted Feb 17, 2016 10:56 AM

    ok another question?   Is there a way to delete an entire set of jobs in Ca7?    like being able to delete all jobs that start with P1?



  • 4.  Re: test runs with CA7 r12 questions

    Posted Feb 17, 2016 12:26 PM
      |   view attached

    Nope—have to use full jobname in a DELETE or PURGE—you can use DBT with a LJOB,JOB=P1* to get a JOBDEL file that would have only P1 jobs in it

     

    MarySue Redd

    Principal Support Engineer

    CA 7

    CA Technologies | 5465 Legacy Drive Suite 700 | Plano, TX 75024-3106

    Office: +1 214 473 1859 | Mobile: +1 817 247 6844 | Mary.Redd@ca.com

     

    <mailto:Mary.Redd@ca.com>[CA]<http://www.ca.com/us/default.aspx>[Facebook]<https://www.facebook.com/CATechnologies>[Twitter]<http://twitter.com/CAInc>[LinkedIn]<http://www.linkedin.com/company/1372?goback=.cps_1244823420724_1>

    P Please consider the environment before printing this e-mail.



  • 5.  Re: test runs with CA7 r12 questions

    Posted Feb 19, 2016 05:33 PM

    And once you have the job information in a file, it's pretty straight forward to use either ISPF EDIT or SORT to create delete statements to run back into the CA-7 batch terminal.  Something like:

    //SYSIN    DD  *

              SORT FIELDS=(22,7,CH,A)

           INCLUDE COND=(31,03,CH,EQ,C'JOB')

               SUM FIELDS=NONE

               END

     

    - Don



  • 6.  Re: test runs with CA7 r12 questions

    Posted Feb 25, 2016 01:39 PM

    These sort statements will take a r11.3 BTI Output(listed below) and format it as input to a BTI

     

    //SYSIN      DD *

      SORT FIELDS=(1,8,CH,A)

      SUM FIELDS=NONE

      INREC FIELDS=(1:2,8,72X)

      INCLUDE COND=(33,3,CH,EQ,C'000')

      OUTFIL HEADER1=(1:'JOB'),REMOVECC

      OUTREC FIELDS=(1:C'PURGE,',1,8,66X)

    /*

     

    OUTPUT OF SORT

    EDIT       WXYZ.TESTS

    Command ===>

    ****** ***************************** Top of Data

    000001 JOB

    000002 PURGE,WXYZBAT1

    000003 PURGE,WXYZBAT2

    000004 PURGE,WXYZBTI

     

    INPUT TO SORT

    1BSTR-00  *** INPUT TO BATCH TERMINAL ***

    /LOGON ********           * GENERATED LOGON *

    LJOB,JOB=WXYZ*

    /LOGOFF * GENERATED LOGOFF *

    0BSTR-00  *** END OF INPUT ***

    1  16056  131454    /LOGON ********

    CA-7.023 - r11.3(    ) OPERATOR IS LOGGED ON TO TERMINAL TBATCH7 AT 13:

    -  16056  131454    LJOB,JOB=WXYZ*

    1LJOB,JOB=WXYZ*

    JOB=WXYZ*                                              DATE=16.056    P

       JOB    ----JCL----   SYSTEM  USR MAIN PROSE  SCHED  --NUMBER OF-   LA

       NAME    ID  MEMBER   -NAME-  -ID -ID- DSNBR  DSNBR  STP DDS RUNS   DA

    WXYZBAT1 005 WXYZBAT1 OPER     000 ALL  *NONE* *NONE* 001 006 0352  160

    WXYZBAT2 005 WXYZBAT2 OPER     000 ALL  *NONE* *NONE* 001 011 0042  153

    WXYZBTI  005 WXYZBTI  OPER     000 ALL  *NONE* *NONE* 002 009 0496  160