× 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.



Amazes me too. I seriously doubt I could have retained a job as long as he has with the attitude and antisocial behavior.

John McKee

-----Original message-----
From: "Paul Nelson" nelsonp@xxxxxxxxxxxxx
Date: Wed, 01 Dec 2010 10:41:11 -0600
To: "'Midrange Systems Technical Discussion'" midrange-l@xxxxxxxxxxxx
Subject: RE: LUD list

<< The sa does not like to get involved with this stuff. And, as I have
posted before, is antisocial.>>

Is he the owner's son? Any administrator that refuses to keep up with
patches, etc. isn't worth keeping on the payroll.

Paul Nelson
Office 512-392-2577
Cell 708-670-6978
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of jmmckee
Sent: Wednesday, December 01, 2010 8:54 AM
To: Midrange Systems Technical Discussion
Subject: LUD list

The shop is at v5r4. No current on PTFs. Not something I am allowed or
responsible for doing. The sa does not like to get involved with this
stuff. And, as I have posted before, is antisocial.

We had a spate of devices that would not connect in 2006. At the time, I
learned that there was a maximum number that could/should be assigned to a
subsystem. I passed that on to the sa, who ignored it. The device issues
continued. He >finally< contacted IBM and was given a procedure to recover
devices that get hung. He was also told to create an additional subsystem,
which he did. Problem went away. It is now back. Three devices, in two
days, so far have been hung.

The procedure from IBM was to do a DMPSYSOBJ OBJ(PASSTHRU#LUD#LIST)
CONTEXT(QSYS) TYPE(0E) SUBTYPE(EF)

scan the spool file for the hung device

If found, vary off the device and then issue this command:
CALL PGM(QSPTLIB/QPARIXEN) PARM('device name')

That works.

My question (sorry about the length of this), does anybody know if the
underlying problem has been addressed by an APAR and PTF?

If, such exists, I >might< be able to get my supervisor to persuade the sa
(who he also directs or tries to) to apply either the latest cum or a
specific PTF.

This is nuts.

Sorry for the rant and length. Just gets frustrating.

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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.