CA InterTest

Expand all | Collapse all

a Unique situation, where Xpediter's CWPCMAIN (pre-processor) step compile listing feeds out to a lib to be used by Intertest

Jump to Best Answer
  • 1.  a Unique situation, where Xpediter's CWPCMAIN (pre-processor) step compile listing feeds out to a lib to be used by Intertest

    Posted 03-09-2017 03:48 PM

    We are trying to kill (so to speak) more than two birds with one stone. We want all listings (whether batch or CICS) to be stored in DDIO's. Now, we have found too many programs have the following copy statements option 'SUPPRESS' being used. Which if we use the post process utility after the IGYCRCTL to store into a DDIO, it will not accept it. But the pre-process utility CWPCMAIN will. It of course calls out to IGYCRCTL and at the same time deal with the SUPPRESS and then stores into the DDIO directly. Now we use Xpediter for batch only. We use INTERTEST for CICS. So when we capture that listing from the pre-processor CWPCMAIN it puts a whole set of CBLs into the listing. Which when you feed the listing thru to INTERTEST it coughs it up (so to speak). So now we are looking for a way to suppress (I know ironic isn't it) the CBLs out of CWPCMAIN so that the listing doesn't have them and INTEREST is happy. If we can do this then the one utility can serve multiple purposes.

    BTW if you know the opposite solution. Where Intertest can be told to ignore the extra info, that would work too.

    Thoughts?

    BTW, yes we could use IF then Else call on the correct things etc. However there seems to be a 'want' to use just the one utility. Besides we would still need to run CWPCMAIN to get by the COPY SUPPRESS issue to store in a DDIO.

    Which would mean running two compiles. Not a pretty picture.



  • 2.  Re: a Unique situation, where Xpediter's CWPCMAIN (pre-processor) step compile listing feeds out to a lib to be used by Intertest

    Posted 03-10-2017 11:23 AM

    A follow up,

    This is what Intertest doesn't like, is there a parm to tell Intertest to ignore or accept them?

    PROCESS(CBL) STATEMENTS:                                       
     CBL NOADV,APOST,ARITH(COMPAT),NOAWO,NOBLOCK0,BUFSIZE(4096)    
     CBL NOCICS,CODEPAGE(37),NOCOMPILE(S),NOCURRENCY,DATA(31)      
     CBL NODATEPROC,NODBCS,NODECK,NODIAGTRUNC,NODLL,NODUMP,NODYNAM 
     CBL NOEXPORTALL,FASTSRT,FLAG(I,I),FLAGMIG4,NOFLAGSTD,LIB      
     CBL LINECOUNT(55),LIST,MAP,NONAME,NSYMBOL(DBCS),NONUMBER      
     CBL NUMPROC(NOPFD),OBJECT,NOOFFSET,OPTIMIZE(STD),OUTDD(SYSOUR)
     CBL PGMNAME(COMPAT),RENT,RMODE(AUTO),NOSEQUENCE,SIZE(16777216)
     CBL SOURCE,SPACE(1),NOSQL,SQLCCSID,NOSSRANGE,NOTERM,NOTEST    
     CBL NOTHREAD,TRUNC(OPT),NOVBREF,NOWORD,XMLPARSE(XMLSS)        
     CBL XREF(FULL),YEARWINDOW(1900),ZWB                           



  • 3.  Re: a Unique situation, where Xpediter's CWPCMAIN (pre-processor) step compile listing feeds out to a lib to be used by Intertest
    Best Answer

    Broadcom Employee
    Posted 03-10-2017 12:22 PM

    Hi Ronald,

     

    We recently had a client that encountered a simulator problem which was resolved by setting CSS parms: PROC($NO)” in their CWPCMAIN utility to suppress the generated CBL statements.



  • 4.  Re: a Unique situation, where Xpediter's CWPCMAIN (pre-processor) step compile listing feeds out to a lib to be used by Intertest

    Posted 03-10-2017 12:30 PM

    Tried it and it seems that Intertest took in the listing and tested fine. Thanks for that confirmation.



  • 5.  Re: a Unique situation, where Xpediter's CWPCMAIN (pre-processor) step compile listing feeds out to a lib to be used by Intertest

    Posted 03-10-2017 12:34 PM

    I realize this is a CA Intertest forum but wondering with removal of the CWPCMAIN generated CBL statements, did the Xpediter use of the stored listing without the CBL statement in DDIO work ok? We're waiting to have a user test that.



  • 6.  Re: a Unique situation, where Xpediter's CWPCMAIN (pre-processor) step compile listing feeds out to a lib to be used by Intertest

    Broadcom Employee
    Posted 03-10-2017 12:47 PM

    I have no feedback on that.