Re:[IDMS-L] Question about CA - HYPER NOTIFICATION - RO20143 IDMS

Discussion created by ca.portal.admin on Jul 27, 2010
- OS getmain problem

This refers to IBM apar OA27291 on z/OS 1.10. If we are going to 1.11
does anyone know if we still need to apply it?

Hoping support will see this.



Jim Rice
ph (404) 506-4148
Fax (404) 506- 4870
Customer Focused/Client Oriented since 1991

This e-mail and any of its attachments may contain proprietary Southern
Company and/or affiliate information that is privileged, confidential,
or protected by copyright belonging to Southern Company and/or its
affiliates. This e-mail is intended solely for the use of the
individual or entity for which it is intended. If you are not the
intended recipient of this e-mail, any dissemination, distribution,
copying, or action taken in relation to the contents of and attachments
to this e-mail is contrary to the rights of Southern Company and/or its
affiliates and is prohibited. If you are not the intended recipient of
this e-mail, please notify the sender immediately by return e-mail and
permanently delete the original and any copy or printout of this e-mail
and any attachments. Thank you.
IDMS 3rd-party providers forum


Re: Question about CA - HYPER NOTIFICATION - RO20143 IDMS - OS getmain problem
"What Chris says is true. The ""VSM USEZOSV1R9RULES"" in the DIAGxx member
of SYS1.PARMLIB dictates in z/os 1.11 how the GETMAIN is used. This
problem was not seen in z/os 1.9 but could happen only if the GETMAIN
storage is almost all used. We have never seen it happen in z/os 1.9,
but does occur in 1.10 z/os. The reason to apply it is that - if someone
changes the default, IDMS will get the problem mentioned in some cases..
usually after a warmstart occurs because we may do a getmain for 8192
bytes or less and under the new 'rules' (not v1R9).. IBM put out an APAR
UA45583 which 'fixed' or introduced the V1R9RULES..
Read that for more information.
We suggest applying the PTF to avoid any occurrence of the 'dirty'
getmain under all operating system configurations.
Ed McKinney CA Technologies