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



ROB: I know that this particular user was part of the qualified job name because the windows pop-up with the error:

The message was:

Job 123456/user-id/JWALK000G started on 8/25/15 at 13:44:45 in subsystem...(The rest of the text not shown)
A character representation of a numeric value is in error (C G D F).

Type reply, press Enter.
Reply [...Form box for entry here..]

The 3rd party software uses JWALK to show a GUI interface instead of green screen for the users that prefer it.

I know that when a Windows FTP script runs a program on the system, the FTP job is running under one user-ID (QUSER I think) and it kicks off another job in batch with the user-ID that opened up the FTP session. Not familiar enough with how these TCP-IP jobs work yet. And maybe the JWALK jobs don't work like other such jobs.

KEN: " I'm not at all familiar with JWALK. But if the job was running as a different user, the dump would be in a QPRTJOB job for that other user."

I looked for the dump under that user's name and it did not work. I also did a WRKJOB JWALK000G *OUTQ and nothing came up. I also did the entire qualified and nothing. Then I did a WRKSPLF [user-id] and there was no dump.

Maybe it printed real fast?

Next time, I'm having the user stay open on that message while I run down everything I can on it to track down this bad data. Just thinking somebody else has been here and might have a shortcut way to find it.

DARRYL: As I thought I stated, I DID have the user enter a "D" to dump the program. I posted this question because I couldn't find the dump.
Good idea to check the logging level, but a "D" should produce the RPG dump, anyway.


PAUL: Thanks so much for the DSPLOG suggestion, I should have thought of that (slapping my face).
I think I may have tried the parameters in your WRKSPLF suggestion but maybe I didn't.
And, I know the error is not JWALK's fault, and not necessarily in the application, I'm sure it's bad data in the files somewhere.
(NOTE: USERS SHOULD NOT COPY FROM A WEB PAGE AND PASTE INTO DATA INPUT)

LUIS: Thanks for the WRKOUT QEXDEBUG mention, I'll try that.

Thank you to everybody for the rapid responses!

Alan


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, August 26, 2015 8:13 AM
To: Midrange Systems Technical Discussion
Subject: Re: How do I find the job associated with a JWALK error

First of all, how did you know that this particular user was part of the qualified job name? Normally it is on regular 5250 based jobs. However (and it's been awhile since I looked at Seagull's JWalk) is it the same thing for a screen scraper like JWalk? Perhaps it runs in a QHTTPSVR job and uses profile handles or some such thing? If the person is still in that job can they do DSPJOB? Or SysReq 3, then option 4?

Will WRKOBJLCK on that user profile show you the job?


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: Alan Cassidy <ACassidy@xxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 08/26/2015 07:41 AM
Subject: How do I find the job associated with a JWALK error
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



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.



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


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.