|
Geez...I wouldn't think that would be too many, even if it was counting the CPYTOSTMF files. You could try a RCLACTGRP ACTGRP(*ELIGIBLE). On Thu, 5 Aug 2004 11:29:25 -0400, "Art Tostaine, Jr." <midrange@xxxxxxxxxxx> said: > I'm using ACTGRP *CALLER. My RPG program calls a CLP to create the > file, then fills it, then calls the same CLP again to send the file, > then starts over. > > The job is doing 20-30 CPYTOSTMF's. Is there something I can run after > the CPYTOSTMF to clean up better? > > Thanks. > > Art Tostaine, Jr. > CCA, Inc. > Jackson, NJ 08527 > > > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of > michaelr_41@xxxxxxxxxxxxxx > Sent: Thursday, August 05, 2004 11:13 AM > To: Midrange Systems Technical Discussion > Subject: RE: Too many files open > > I wonder if a RCCLACTGRP would help, assuming it's running in a named > activation group. Also, I'll bet the system is counting each file in the > CPYTOSTMF as an open file. > > On Thu, 5 Aug 2004 11:09:45 -0400, "Art Tostaine, Jr." > <midrange@xxxxxxxxxxx> said: > > There are less than 20 files open when I view the job, the system is > not > > really doing anything (this runs at 5am before most people start), and > > there is 1 gig of memory. > > > > V5R1. > > > > Thanks. > > > > Art Tostaine, Jr. > > CCA, Inc. > > Jackson, NJ 08527 > > > > > > -----Original Message----- > > From: midrange-l-bounces@xxxxxxxxxxxx > > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Al Barsa > > Sent: Thursday, August 05, 2004 10:55 AM > > To: Midrange Systems Technical Discussion > > Subject: Re: Too many files open > > > > > > > > > > > > > > Art: > > > > I don't know of a specific maximum number of open files, but (in many > > cases) the architecture of the system limits you by memory. So three > > questions: > > > > 1.) How many open files in this job. > > 2.) How much memory on the system. > > 3.) Is the system generally busy of idle, apart from your job. > > > > Al > > > > Al Barsa, Jr. > > Barsa Consulting Group, LLC > > > > 400>390 > > > > "i" comes before "p", "x" and "z" > > e gads > > > > Our system's had more names than Elizabeth Taylor! > > > > 914-251-1234 > > 914-251-9406 fax > > > > http://www.barsaconsulting.com > > http://www.taatool.com > > http://www.as400connection.com > > > > > > > > > > > > "Art Tostaine, > > > > Jr." > > > > <midrange@link400 > > To > > .com> "'Midrange Systems Technical > > > > Sent by: Discussion'" > > > > midrange-l-bounce <midrange-l@xxxxxxxxxxxx> > > > > s@xxxxxxxxxxxx > > cc > > > > > > > > Subject > > 08/05/2004 10:45 Too many files open > > > > AM > > > > > > > > > > > > Please respond to > > > > Midrange Systems > > > > Technical > > > > Discussion > > > > <midrange-l@midra > > > > nge.com> > > > > > > > > > > > > > > > > > > > > In a long "working ok" process, I am receiving this error now: > > > > 2800 - CPYTOSTMF > FROMMBR('/QSYS.LIB/QTEMP.LIB/EDI214.FILE/EDI214.MBR') > > > > TOSTMF('/TMP/EDI856.TXT') STMFOPT(*REPLACE) DBFCCSID(37) > > > > STMFCODPAG(*PCASCII) > > > > Too many open files for process. > > > > > > Additional Message Information > > > > > > > > Message ID . . . . . . : CPFA0A4 Severity . . . . . . . : > 40 > > > > Message type . . . . . : Diagnostic > > > > Date sent . . . . . . : 08/05/04 Time sent . . . . . . : > > 05:05:25 > > > > > > Message . . . . : Too many open files for process. > > > > Cause . . . . . : The process maximum number of open files has been > > reached. > > No additional files can be opened. > > > > Recovery . . . : Close some of the open files or wait until some > > files have > > been closed and then retry the operation. > > > > > > > > I added a RCLRSC before the CPYTOSTMF, but that didn't help things. > > > > This CLP copies files to the IFS (lots of them), then uses Brad Stones > > GETURI to transmit them to a web service. > > > > Any ideas? > > > > > > Art Tostaine, Jr. > > CCA, Inc. > > Jackson, NJ 08527 > > > > -- > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > > list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > > > > > > > -- > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > > list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > > > -- > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > > list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > > -- > > michaelr_41@xxxxxxxxxxxxxx > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > -- michaelr_41@xxxxxxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.