Topic
  • 6 replies
  • Latest Post - ‏2015-02-13T18:45:19Z by boyerpl
SystemAdmin
SystemAdmin
849 Posts

Pinned topic Parameter to allow multiple assembler programs per request

‏2013-02-14T15:54:29Z |
I recall there was a Common.cfg setting to allowed batching up requests on a single GUI interaction. The question is what is it ? The Customer has 1,400 ASSEMBLER programs and management does not want to use any extensions.
Updated on 2013-02-19T16:23:19Z at 2013-02-19T16:23:19Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    849 Posts

    Re: Parameter to allow multiple assembler programs per request

    ‏2013-02-14T16:48:47Z  
    Edit Common.cfg (on Windows), find the MVS section and add maxAsmScans = some_number.
    There is no upper limit for this setting, therefore, if you can have 1000 batch jobs submitted, it will do it.
  • SystemAdmin
    SystemAdmin
    849 Posts

    Re: Parameter to allow multiple assembler programs per request

    ‏2013-02-14T17:00:53Z  
    Edit Common.cfg (on Windows), find the MVS section and add maxAsmScans = some_number.
    There is no upper limit for this setting, therefore, if you can have 1000 batch jobs submitted, it will do it.
    Thank you Joan.
  • SystemAdmin
    SystemAdmin
    849 Posts

    Re: Parameter to allow multiple assembler programs per request

    ‏2013-02-19T16:23:19Z  
    Thank you Joan.
    I have tried the following settings, but the wizard does not seem to take more that 50 characters or so. I am missing anything ?
    MVS
    HLQ = HLQ.DMH.ZOSSCAN
    userHLQ =
    hfsRootDirectory = /usr/lpp/dmh
    asmLoadLibrary =
    maxAsmScans = 25
    leLoadLibrary = CEE.SCEERUN
    leLanguage = $L{mvsLeLanguage}
    jobCard1 = //WSSTUDIO JOB 00000000,'RATIONAL AA',
    jobCard2 = // CLASS,A,MSGCLASS=H,MSGLEVEL=(1,0),
    jobCard3 = // REGION=4M
    jobCard4 = //* DEFAULT JOB CARD
    ispfHLQ = ISP
    fileEncoding = $L{mvsFileEncoding}
  • boyerpl
    boyerpl
    222 Posts

    Re: Parameter to allow multiple assembler programs per request

    ‏2013-10-18T17:23:22Z  
    I have tried the following settings, but the wizard does not seem to take more that 50 characters or so. I am missing anything ?
    MVS
    HLQ = HLQ.DMH.ZOSSCAN
    userHLQ =
    hfsRootDirectory = /usr/lpp/dmh
    asmLoadLibrary =
    maxAsmScans = 25
    leLoadLibrary = CEE.SCEERUN
    leLanguage = $L{mvsLeLanguage}
    jobCard1 = //WSSTUDIO JOB 00000000,'RATIONAL AA',
    jobCard2 = // CLASS,A,MSGCLASS=H,MSGLEVEL=(1,0),
    jobCard3 = // REGION=4M
    jobCard4 = //* DEFAULT JOB CARD
    ispfHLQ = ISP
    fileEncoding = $L{mvsFileEncoding}

    You should be able to specify a data set name with a wildcard, like:   MYDSN.SOURCE(ASM*)

    As long as ASM* matches 25 or fewer member names, the scans will be submitted.  Otherwise, you may need a more restrictive pattern like ASMA*.

  • RavikanthChavali
    RavikanthChavali
    51 Posts

    Re: Parameter to allow multiple assembler programs per request

    ‏2015-02-13T16:29:55Z  
    • boyerpl
    • ‏2013-10-18T17:23:22Z

    You should be able to specify a data set name with a wildcard, like:   MYDSN.SOURCE(ASM*)

    As long as ASM* matches 25 or fewer member names, the scans will be submitted.  Otherwise, you may need a more restrictive pattern like ASMA*.

    If it is going to submit jobs for each member (25 jobs), how could we change the jobName for each member ? 

    We have a restriction that will not parallely execute more than one job with the same jobName under the same id. 

    Thank you,

    Ravikanth Chavali

    Updated on 2015-02-13T17:02:16Z at 2015-02-13T17:02:16Z by RavikanthChavali
  • boyerpl
    boyerpl
    222 Posts

    Re: Parameter to allow multiple assembler programs per request

    ‏2015-02-13T18:45:19Z  

    If it is going to submit jobs for each member (25 jobs), how could we change the jobName for each member ? 

    We have a restriction that will not parallely execute more than one job with the same jobName under the same id. 

    Thank you,

    Ravikanth Chavali

    There's not currently a way to use the web user interface to submit the jobs with different names.

    A workaround would be to log onto TSO, copy one of the jobs, and use it as a template for manually creating the JCL you need for running the scans in parallel.  Those jobs could also have more than one scan step.