ODF Banner Exit performance on V10.1

[Nolan]

Good day,

We have upgraded to V10.1 from V9.5 in our test system and have found an almost 35% increase in processing time when using our banner Exit.  There were no changes to the exit between V9.5 and V10.1, we recompiled using the new modules and see a drastic impact on throughput.   Anyone else had a similar experience?

It is not a complex banner exit, we read the customer vars for some flags, convert some text to big letters, and push out Dist address info/Dist ID/Report ID/Jobname.

[Justin Derrick]

Any chance there's an opportunity for optimizing your exit with different compiler options?  I know in most C-language compilers, there's an 'optimization' option with different levels / functionality.

-JD.

[Nolan]

Using the exact options provided by IBM.  I don't believe there is much we can change for the banner exit.

//COBOL2  EXEC PGM=IGYCRCTL,REGION=0M,PARM='DLL,LIST,MAP,OBJ,RENT,
//             TRUNC(OPT),NOSEQ,XREF,EXP,THREAD,PGMN(LM)'         


//LKED     EXEC PGM=IEWL,COND=(4,LT),                   
//     PARM='CASE=MIXED,COMPAT=ZOSV1R11,OPTIONS=OPTS'   
...
//OPTS     DD  *                                         
    XREF                                                 
    AMODE=31,MAP                                         
    RENT,DYNAM(DLL)                                     

[scottnys]

Something to look forward to - Not.  The ARSBANNER seems to be the worst part of the last couple of upgrades.