Alan,
1) Do a DSPLOG, F4, change your start date and time a few minutes before the time of the error and find the name of the job that ended.
2) Do a WRKSPLF, F4, change user to *all and USER DATA to match the name of the job from above.
3) F18 bottom, you should see any spool files related to the job.
We use Jwalk here, the error you are seeing is an application error and not a JWALK error.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Cassidy
Sent: Wednesday, August 26, 2015 7:41 AM
To: Midrange Systems Technical Discussion
Subject: How do I find the job associated with a JWALK error
Good morning (or afternoon) everybody,
I have searched the midrange-l archives and google for this but nothing is specific enough. I can't believe nobody came across this before.
Okay, our third party software uses JWALK for the GUI to the users.
One of our users got an error. Char representation of a numberic value is in error (C G D F). I had the user enter a "D", cancel out, and continue with other work she was doing.
But I could not find the dump! WRKSPLF [user-id] got me no spool files. I thought I would see something because the user id was part of the "qualified job name".
How can I find the job associated with that message? And/or at least that dump?
My plan now is to have her hold while I dig into the log for the qualified job there, and go from there.
Thanks all
Alan
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
Sent: Monday, August 24, 2015 10:52 AM
To: Midrange Systems Technical Discussion
Subject: If it ain't broke, don't fix it
I did not want to pollute the thread "If you have SSDs, please read".
Some years ago, PTFs stopped being applied here. Much like "if it ain't broke". We had an application that did screen scraping. Long gone. A Client Access PTF broke the application. A somewhat critical application, as it turned out. The SA may or may not have contacted the vendor of the pc software. But, what was done was the PTF was backed out.
After that, no CUMEs were installed. Only PTFs identified by service advisor.
Various people in command hierarchy, I have no idea how high up, set that policy.
Potentially very dumb policy. That was why I was a little hesitant to install PTFs suggested by Scott K that corrected errors with ssh. I am glad I did, as the enhanced error handling made a number of transfers performed subsequently a LOT nicer.
Clueless management too far removed from the system making policy decisions.
"Don't confuse me with facts, I have already made up my mind".
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.
--------------------------------------------------------------------------------
Confidentiality Notice: This email may contain confidential information or information covered under the Privacy Act, 5 USC 552(a), and/or the Health Insurance Portability and Accountability Act (PL 104-191) and its various implementing regulations and must be protected in accordance with those provisions. It contains information that is legally privileged, confidential or otherwise protected from use or disclosure. This e-mail message, including any attachments, is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. You, the recipient, are obligated to maintain it in a safe, secure and confidential manner. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Thank you.
--------------------------------------------------------------------------------
--
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.
midrange.com
