Re: remote 520 questions (more)

Thanks. One two hour conference call (think theme from Gilligan's Island,
with small change) dealt with possibility/probability of systems failures
because no hardware support was paid for. Not just IBM stuff. They acted
like the system will immediately fail solely because maintenance contract
was dropped. The remote 520 has been sitting essentially unused for two
years. Hospital was forced to a new system back then, and then forced onto
yet another system. I can't imagine how messed up things are at that place.

Issue was whether the remote v5r3 would retain spool data. Talk somehow
got directed to system reload - but if only one drive failed - and it was
noticed and attended to, there would not be an issue. They appear to think
system is going to self-destruct. From what I have seen, that would be
more likely for the new and improved system.

John McKee

On Fri, Jan 9, 2015 at 11:09 AM, <rob@xxxxxxxxx> wrote:

I can't speak for others but we often can't remember everyone's setup. Let
me see if I can figure this out. You have two machines. A local and a
remote. The remote is a 520 running V5R3. The local is also a 520 but
it's running V5R4.

And you asked if the remote loses a drive if there might be any data loss.
If it only loses ONE drive then there shouldn't be any data loss. I'm
going to assume that you are not using the hot spare option. After that
drive fails you really need to replace the drive. Well, if the
decommisioning can be measured in under a week after the disk failure then
it's a business decision as to whether or not it's an acceptable risk.




Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: John McKee <jmmckee@xxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 01/09/2015 11:37 AM
Subject: remote 520 questions (more)
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I was asked mor questions.

As part of the (in)famous "decommissiong", we continue to find issues. For
example, I am looking at an output that has 171423 files. There are other
queues with a large number as well, but probably not as many. Cache
battery is gone.

Since we recently had cache battery and hard drive replaced on local
system, I feel confident (maybe foolishly?) that this isn't an issue, but
I
was asked. If a remote drive craps out - it is in a RAID set, is there
any
potential data loss? They are keeping things in output queues because
there is no alternative.

They need to keep the content, which brings up the related question, and I
am thinking no easy answer here. Remote is v5r3. Can the spool files be
converted to PDF? I am cringing at the thought of doing this for 171423
or
even 11,736 files. But, I have to ask. Does SPOOLTOOL have this
capability?

Due to large outques and I don't know how much actual junk, if SPOOLTOOLS
could do conversion to PDF (again, on v5r3 system), could it be installed
without pushing Dasd over the edge? System is at 88.5142 of 317.1G.

I created a user profile on local 520 (v5r4) with same user name and
password as my profile ob the remote system. Still could not open a DDM
file. Same error and reason code - 17. Maybe there is an exit program
involved, but command to look at exit programs has slipped away from
active
memory. Maybe it is just file authority. My login is tied to a group
profile so when I sign on, I have needed authority to access files. Maybe
whatever job provides DDM service needs that authority - if so, what
profile is that?

I deeply appreciate your patience and assistance. This whole process is
rapidly approaching the looney stage.

John McKee
--
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.