× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. February 2010

RE: The dreaded system full, now what.

A few other alternatives that maybe much easier.

Do a manual IPL, and you can come up to a restricted state. This is the
least amount of jobs that will be on the system ever, and you will be able
to look at what you can delete from the console. You should be able to find
some stuff. Even if you found no space, just doing the IPL will clean up
temporary storage to give you a little breathing room. You can perm apply
PTFs if you need space, look for *JRNRCVs that you might no longer require,
look for some *SAVFs. This should give you a little space so that you can
then run RTVDSKINF.

Pete

Pete Massiello
iTech Solutions
http://www.itechsol.com

Add iTech Solutions on Facebook:
http://www.facebook.com/group.php?gid=126431824120
Add iTech Solutionw on LinkedIn: http://www.linkedin.com/groups?gid=2206093





-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of bll1981
Sent: Monday, February 08, 2010 2:24 PM
To: Midrange Systems Technical Discussion
Subject: Re: The dreaded system full, now what.

Sorry its a tough one to explain.

1) If the system is so full that another job cannot be created, then you
need to find a way to submit commands. FTP quote is a method I have used to
accomplish this.Once you have created some "breathing room" through the use
of FTP commands, now you can try to grab a 5250 interactive session and
proceed to really analyze the problem.

2) In some situations of prolonged AUX storage max-outs, the OS will kill
off the system dispatch job (the name escapes me, but its one of those in
QSYSWRK). If this job dies, assignment of new jobs pretty much dies as
well......until after you IPL the box. In order to get a session, you have
to free a table entry thats already in use, otherwise you will connect but
sit at the signon processing screen indefinitely. So in this case I position
my console login at the "locked" signon processing screen, then proceed to
kill off a job or something consuming a table entry (spool files) with FTP
commands. Once the existing job dies, the waiting interactive console
session grabs the open job table entry and you are in! Next you would
prepare for IPL and in most situations a MSD for IBM.

Hope this experience gives you some ideas the next time you run into AUX
storage issues.

Bradford Lovelady




________________________________
From: Jack Kingsley <iseriesflorida@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Mon, February 8, 2010 11:52:18 AM
Subject: Re: The dreaded system full, now what.

With FTP your you talking using quote rcmd to do some sort of cleanup that
would allow you a telnet session then eventually or ??

On Mon, Feb 8, 2010 at 12:04 PM, bll1981 <bll1981@xxxxxxxxxxxxx> wrote:

You have to rename the QCURRENT member in QAEZDISK to something unique for
that RTVDSKINF iteration, or copy the QAEZDISK file over to something else
you name. The PRTDSKINF command will analyze and print whatever is loaded
in
the QUSRSYS/QAZDISK.QCURRENT location. You just have to manually
facilitate
moving the archived members or file into QUSRSYS/QAZDISK.QCURRENT.



________________________________
From: Jack Kingsley <iseriesflorida@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Mon, February 8, 2010 9:00:25 AM
Subject: Re: The dreaded system full, now what.

Rob, here is the drawback, unless you have examined the current one and
somewhat know what is going on the new one will overlay the previous data
and your back at square one in figuring it out.

On Mon, Feb 8, 2010 at 9:45 AM, <rob@xxxxxxxxx> wrote:

"quickly" is they key word. RTVDSKINF is your answer (as you figured)
but
it's not quick. If you read the help on RTVDSKINF it tells you what
files
it creates and how to retain that data to do comparisons.


Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jack Kingsley <iseriesflorida@xxxxxxxxx>
To: Midrange Systems Technical Discussion <MIDRANGE-L@xxxxxxxxxxxx>
Date: 02/08/2010 09:10 AM
Subject: The dreaded system full, now what.
Sent by: midrange-l-bounces@xxxxxxxxxxxx



I recently had a system that had filled up it's disk storage due to a
run
away job and an errant qsysprt printer file set to nomax on records, the
system was basically locked up. Does anyone have specific instructions
on
what they do when a problem such as this comes about. I did a normal
IPL
and did not know what I had at the time until the IPL had completed and
I
was able to gain access to a signon screen. Once signed on I did a
quick
wrksyssts and could see what was going on. At that time I ended all
subsystems to get the box in a restricted state in order to diagnose
what
was going on. I happened to stumble on the spooled file that had the
dreaded +++++ for pages. Once I deleted the spooled file the disk
storage
went down, but then I get bit by the qrclsplstg system value being set
to
*NONE, this caused a massive locking problem on members in QSPL library
and
jobs that could not then run due to qpjoblog locks. If I had not
stumbled
on the spooled file I am not sure how long it would have taken me to
figure
out the(where has mydisk space gone) situation. I don't believe there
is
a
command to quickly diagnose previous rtvdskinf(s) either and or a
command
to
show which reports take up the most disk storage(not at least quckly )
anyways.
--
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.
--
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.