Automated Testing

Automated Testing

Automated Testing

Build an automated testing process to enable continuous integration of your hybrid cloud applications including z/OS

 View Only
  • 1.  Installation default for output limitation

    Posted 08/28/13 08:20 AM

    It happens every now and then on our RDz UT system that when we test a faulty program containing an endless loop with debug output, the spool file quickly becomes flooded. This can lead to a total blocking of the system.

    We have now added LIMIT=(nn,CANCEL) to the JOB statement in order to prevent this. This works fine: the job will be canceled when it exceeds the specified number of output lines.

    However, it may happen that we submit a job and forget to set the LIMIT. So I would like to use an installation default as described in http://publib.boulder.ibm.com/infocenter/zos/v1r11/index.jsp?topic=/com.ibm.zos.r11.hasa300/excess.htm

    My question: I cannot find the place where this ESTLNCT installation default has to be specified. Any hints?

    unsavvy


  • 2.  Re: Installation default for output limitation

    Posted 08/28/13 12:47 PM

    I searched the active parmlibs on my system and found ESTLNCT and others to be specified in the JES2PARM member. 

    In ISPF you can type on any command line DDLIST <enter> and then use the PARMLIB command to view your parmlibs.  Back up the JES2PARM member before changing it because errors can cause problems starting JES2 and you can start JES2 with the backup copy if necessary (eg: S JES2,MEMBER=JES2BACK).

    A reference for the ESTLNCT, for example, is at http://publib.boulder.ibm.com/infocenter/zos/v1r11/index.jsp?topic=/com.ibm.zos.r11.hasa300/excess.htm

    RDzDoug


  • 3.  Re: Installation default for output limitation

    Posted 08/28/13 01:38 PM

    Thank you for your quick and helpful response!

    I found the JES2PARM member in ADCD.Z111.PARMLIB, and it contained the following

    ESTLNCT  NUM=12,INT=6000,OPT=0

    According to the parameter description for ESTLNCT, OPT=0 means that the job is allowed to continue, so this does not seem to have any effect, does it?

    I will copy the member over to our USER.PARMLIB and modify ESTLNCT to our needs.

    And one more question: I haven't found a description how ESTLNCT interacts with ESTBYTE and ESTPAGE. I assume that the job takes the action requested by the OPT parm whenever and every time when one of the limits is reached?

     

     

    unsavvy