Wow, that didn't format correctly the first time. Hopefully this time is better.
Here are all the documented and undocumented 'Dirty' parameters I know of. These go in the DIAGxx member of SYS1.PARMLIB. These are NOT recommended for production or even development environments. Try them on a TEST LPAR to shake out any problem areas. Traps Name(IeaCmSetV, /* Ensure disabled CMSET caller */ IeaInitArSrb, /* Initialize registers for SRBs */ IeaInitRegsTask, /* Initialize registers for TCBs */ IeaSpinLockV, /* Verify spin lock environment */ IeaScheduleV, /* Verify schedule environment */ IeaScheduleTrace, /* Trace SCHEDULE & IEAMSCHD */ IeaRpsgnlTrace, /* Trace RPSGNL calls */ /* Sloooow IgvCpoolGetV, /* Validate CPOOL GET environment */ IgvInitCpool, /* Initialize CPOOL GET elements */ IgvInitGetmain, /* Initialize GETMAINed storage */ IgvInitFreemain, /* Initialize FREEMAINed storage */ IarSt64InitGet, /* Initialize gotten 64-bit stg. */ IarSt64InitFree, /* Initialize freed 64-bit stg. */ IarCp64InitGet, /* Initialize gotten 64-bit cells */ IarCp64InitFree /* Initialize freed 64-bit cells */ ) Chris Blaicher Technical Architect Software Development Syncsort Incorporated 50 Tice Boulevard, Woodcliff Lake, NJ 07677 P: 201-930-8234 | M: 512-627-3803 E: [email protected] -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Thursday, November 19, 2015 1:15 PM To: MVS List Server 2 <[email protected]> Subject: Re: Change in GETMAIN behavior On 2015-11-19, at 11:03, Elardus Engelbrecht wrote: Why does the option for "dirty" GETMAIN (I forget the correct name) remain undocumented, despite its value for testing? -- gil
