Hmmmm maybe MemLimit and SHMemMax on OMVS segment are also good parms to check/increase.
Lucas On May 7, 2016 06:06, "Phil Smith III" <li...@akphs.com> wrote: > Rob Schramm offered: > >ASSIZE will set the user limit for storage. Set via RACF. > > Still no, unless I misunderstood (quite possible!): > > DEFAULT-GROUP=SYS1 PASSDATE=14.197 PASS-INTERVAL=N/A PHRASEDATE=N/A > ATTRIBUTES=SPECIAL OPERATIONS > > ATTRIBUTES=AUDITOR > > REVOKE DATE=NONE RESUME DATE=NONE > > LAST-ACCESS=16.127/22:59:36 > > CLASS AUTHORIZATIONS=NONE > > NO-INSTALLATION-DATA > > NO-MODEL-NAME > > LOGON ALLOWED (DAYS) (TIME) > > --------------------------------------------- > > ANYDAY ANYTIME > > GROUP=SYS1 AUTH=USE CONNECT-OWNER=IBMUSER CONNECT-DATE=11.133 > > CONNECTS=19,235 UACC=NONE LAST-CONNECT=16.127/22:59:36 > > CONNECT ATTRIBUTES=NONE > > REVOKE DATE=NONE RESUME DATE=NONE > > SECURITY-LEVEL=NONE SPECIFIED > > CATEGORY-AUTHORIZATION > > NONE SPECIFIED > > SECURITY-LABEL=NONE SPECIFIED > > > > OMVS INFORMATION > > ---------------- > > UID= 0000000003 > > HOME= /u/something > PROGRAM= /u/vendor/bash/bin/bash > > CPUTIMEMAX= NONE > > ASSIZEMAX= 2147483647 > > FILEPROCMAX= NONE > > PROCUSERMAX= NONE > > THREADSMAX= NONE > > MMAPAREAMAX= NONE > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN