I thought there would be the flags, Ed. So thanks for confirming.

It just occurred to me that a useful query an installation could run would 
go something like this:

Pick up all the CICS regions in SMF 30 - using the Usage section to pick 
up their CICS release.
Compare the MEMLIMIT in the same SMF 30 (including reason flags) to the 
one recommended for the release they're going to.
Factor any changes required into the migration plan.

And the reason 1 is necessary is because quite a few shops have multiple 
CICS levels, at least transitionally.

(Or at very least I could build it into my code - with the 
release-specific MEMLIMIT minima hardcoded. I already report Usage section 
data in a separate report and MEMLIMIT/reason for jobs and steps when I 
study them.)

Cheers, Martin

Martin Packer,
zChampion, Principal Systems Investigator,
Worldwide Banking Center of Excellence, IBM

+44-7802-245-584

email: [email protected]

Twitter / Facebook IDs: MartinPacker
Blog: 
https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker



From:   Ed Jaffe <[email protected]>
To:     [email protected]
Date:   19/04/2014 00:59
Subject:        Re: MEMLIMIT best practice
Sent by:        IBM Mainframe Discussion List <[email protected]>



On 4/18/2014 12:02 PM, Martin Packer wrote:
> BTW SMF 30 also has the limit and how obtained in it. So you can see 
what
> an individual job / address space can get at and why.

As one might imagine, the system control block also contains the source 
of the MEMLIMIT:

6 RAXLVMemLimS  FIXED(8) RXZ,   /* Source of Address Space
                                    Memory limit       @P5C*/

DCL RAXLVSMF  FIXED(8) CONSTANT(1);/* MEMLIMIT set by SMF
                                       either in SMFPRMxx or by use
                                       of SMF default value=0 @P8C*/
DCL RAXLVJCL  FIXED(8) CONSTANT(2);/* MEMLIMIT set by the JCL @P5C*/
DCL RAXLVREG0 FIXED(8) CONSTANT(3);/* MEMLIMIT Unlimited based on
                                        REGION=0 specification @P5C*/
DCL RAXLVUSI  FIXED(8) CONSTANT(4);/* MEMLIMIT set by IEFUSI @P5C*/
DCL RAXLVOMVS FIXED(8) CONSTANT(5);/* MEMLIMIT set by UNIX OMVS
                                        segment @P5C*/
DCL RAXLVSETR FIXED(8) CONSTANT(6);/* MEMLIMIT set by UNIX
                                        setrlimit @P5C*/
DCL RAXLVSPW  FIXED(8) CONSTANT(7);/* MEMLIMIT set by UNIX spawn
@P5C*/
DCL RAXLVSETO FIXED(8) CONSTANT(8);/* MEMLIMIT set by UNIX
                                        SETOMVS command @P5C*/
DCL RAXLVAUTH FIXED(8) CONSTANT(9);/* MEMLIMIT set by authorized
                                        application modification@P5C*/
DCL RAXLVURG  FIXED(8) CONSTANT(10);/*Special case of MEMLIMIT
                                       getting set in IEFSMFIE
                                       (IEFUSI set REGION size) @08A*/
DCL RAXLVBAD  BIT(8) CONSTANT('FF'X);
                                     /* Error setting MEMLIMIT */
                                     /* (for debug purposes) @P5C*/

-- 
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN



Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to