Any challenges with setting CSCBLOC to ABOVE

[Lizette Koehler]

Just a curiosity. Some shops are still coding CSCBLOC=BELOW but the default at
2.1 is ABOVE

Description under MAXUSER States:

However, too large a buffer can cause the system to allocate more system
resources than are needed during a given IPL. The excessive allocation of system
resources because of incorporating too large a buffer can lead to potential
problems such as the following examples:

The specification of MAXUSER in conjunction with CSCBLOC=BELOW and RSVSTRT
can cause the system to allocate excessive storage below 16 M. See CSCBLOC for
additional details.
An aggressively large MAXUSER, RSVSTRT, and RSVNONR can cause the system to
allocate an excessive amount of storage, which can potentially lead to a wait
state 204 reason 008. (Wait state 204 with reason 008: An error occurred during
allocation initialization; the system could not obtain storage for device
information.) The system enters a non-restartable wait state 204 at IPL time.




Lizette Koehler
statistics: A precise and logical method for stating a half-truth inaccurately

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Anthony Thompson]

The challenges are if you have any locally-written programs or 3rd-part vendor-supplied software that assume the CSCB (Command Step Control Block, generally used to implement started task operator commands) is in 24-bit storage.

Either contact the vendor or test in a non-productive environment, such as a testplex.

Ant.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler
Sent: Wednesday, 2 May 2018 12:42 PM
To: IBM-***@LISTSERV.UA.EDU
Subject: Any challenges with setting CSCBLOC to ABOVE

Just a curiosity. Some shops are still coding CSCBLOC=BELOW but the default at
2.1 is ABOVE

Description under MAXUSER States:

However, too large a buffer can cause the system to allocate more system resources than are needed during a given IPL. The excessive allocation of system resources because of incorporating too large a buffer can lead to potential problems such as the following examples:

The specification of MAXUSER in conjunction with CSCBLOC=BELOW and RSVSTRT can cause the system to allocate excessive storage below 16 M. See CSCBLOC for additional details.
An aggressively large MAXUSER, RSVSTRT, and RSVNONR can cause the system to allocate an excessive amount of storage, which can potentially lead to a wait state 204 reason 008. (Wait state 204 with reason 008: An error occurred during allocation initialization; the system could not obtain storage for device
information.) The system enters a non-restartable wait state 204 at IPL time.




Lizette Koehler
statistics: A precise and logical method for stating a half-truth inaccurately

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Lizette Koehler]

Thanks,

I am not sure how I would check that out, but I will see what I can do.

Lizette

Post by Anthony Thompson
-----Original Message-----
Anthony Thompson
Sent: Tuesday, May 01, 2018 8:36 PM
Subject: Re: Any challenges with setting CSCBLOC to ABOVE
The challenges are if you have any locally-written programs or 3rd-part
vendor-supplied software that assume the CSCB (Command Step Control Block,
generally used to implement started task operator commands) is in 24-bit
storage.
Either contact the vendor or test in a non-productive environment, such as a testplex.
Ant.
-----Original Message-----
Behalf Of Lizette Koehler
Sent: Wednesday, 2 May 2018 12:42 PM
Subject: Any challenges with setting CSCBLOC to ABOVE
Just a curiosity. Some shops are still coding CSCBLOC=BELOW but the default at
2.1 is ABOVE
However, too large a buffer can cause the system to allocate more system
resources than are needed during a given IPL. The excessive allocation of
system resources because of incorporating too large a buffer can lead to
The specification of MAXUSER in conjunction with CSCBLOC=BELOW and
RSVSTRT can cause the system to allocate excessive storage below 16 M. See
CSCBLOC for additional details.
An aggressively large MAXUSER, RSVSTRT, and RSVNONR can cause the system
to allocate an excessive amount of storage, which can potentially lead to a
wait state 204 reason 008. (Wait state 204 with reason 008: An error occurred
during allocation initialization; the system could not obtain storage for
device
information.) The system enters a non-restartable wait state 204 at IPL time.
Lizette Koehler
statistics: A precise and logical method for stating a half-truth inaccurately

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN