Maybe D OMVS,LIMITS,PID=??? will give you what you want.
Just a guess asking on the OE listserv will likely get a better answer.
If you are bumping up against MAXFILEPROC just raise it.
We set it to 64K a while ago.
/********************************************************************/
/* */
/* Specify the maximum number of file descriptors that a single */
/* user is allowed to have concurrently active or allocated. */
/* */
/* Notes: */
/* */
/* 1. This parameter is the same as the Open_Max variable */
/* defined in POSIX 1003.1. */
/* 2. Minimum value is 3. */
/* 3. Maximum value is 131072. @DGC*/
/* 4. If this parameter is not provided, the system default */
/* value for this parameter is 2000. */
/* */
/* Note: There is no system wide limit on total active descriptors. */
/* */
/* This value can be set for individual users in the OMVS segment */
/* of their user profile with the FILEPROCMAX parameter. */
/* */
/********************************************************************/
MAXFILEPROC(64000)
Health Checker will catch this one being too low. We raised it on R6
when this check tripped.
BPXH003I z/OS UNIX System Services is configured using OMVS=(6T,6S)
which correspond to the BPXPRMxx suffixes. The owner specification for
IBM Health Checker for z/OS USS_MAXSOCKETS_MAXFILEPROC is 64000,64000.
* Low Severity Exception *
BPXH032E MAXFILEPROC value is too low.
Explanation: MAXFILEPROC value of 2000 was found. MAXFILEPROC should
be at least 64000. If MAXFILEPROC is set too low you can run out of
usable file descriptors.
System Action: The system continues processing.
Operator Response: Report this problem to the system programmer.
System Programmer Response: MAXFILEPROC can be raised using the
'SETOMVS MAXFILEPROC=xxxx' command.
Problem Determination: N/A
Source: z/OS UNIX System Services
Reference Documentation: See z/OS UNIX System Services Planning
Automation: N/A
Check Reason: If MAXSOCKETS or MAXFILEPROC are set too low you can
run out of usable sockets or file descriptors respectively.
BPXH035I The value of 64000 for MAXSOCKETS (AF_INET) meets the minimum
owner suggestion of 64000.
Best Regards,
Sam Knutson, GEICO
Performance and Availability Management
mailto:[EMAIL PROTECTED]
(office) 301.986.3574
"Think big, act bold, start simple, grow fast..."
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Ward, Mike S
Sent: Tuesday, July 10, 2007 5:26 PM
To: [email protected]
Subject: Open file under omvs
Hello all, I keep getting this error on Z/os 1.7
+BIP4064W SEPQBRK FDR 24 OPERATING SYSTEM ERROR 'EDC5124I Too many open
017
files.' OPENING TRACE FILE '/mqtraces/cbtrace/pfdrcatch.txt' FOR TRAC
E NODE 'FDR_MESSAGE_FLOW.Catch Trace'. : ImbTraceNode(411)
Before I go changing PBX parms is there any way I can see who has files
open and how many?
Thanks
Mike
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
