With all due respect to the President of my sister user group (that had a
fabulous cruise this summer, worth flying in for - despite the fact that
the four LISUG folks had no reservations), building LF's over QHST files is
potentially dangerous.
I suspect, but do not absolutely know, that QHST files (PF) were designed
to not have LF's built over them, and this potentially would break the
system's "CLEANUP" function. Potentially an OPNQRYF over multiple QHST
files (limited to 32 files) would be a better idea, and would go away at
EOJ. (BTW, I just spoke to Pete, and he says that CLEANUP would gracefully
send an error message that it can't CLEANUP that file, however I would note
that if never cleaned up, that file would become *BOATANCHOR.)
Note that the system value QHSTLOGSIZ was *WAYTOOLOW for many releases.
For most systems, even increasing it to the maximum size was still too low.
After the idiot at COMMON who talks about system values bitched for many
years, IBM trivially increased the maximum size in V5R1 (still way to low),
and in V5R4 IBM provided us with a larger number of digits (that they
always said was impossible [reference QAUTLVL and QAUDLVL2 in V5R3.) If
you at any lower release to V5R4, change the default to as large as the
system will allow.
Al Barsa, Jr.
Barsa Consulting Group, LLC
400>390
"i" comes before "p", "x" and "z"
e gads
Our system's had more names than Elizabeth Taylor!
914-251-1234
914-251-9406 fax
http://www.barsaconsulting.com
http://www.taatool.com
http://www.as400connection.com
"Pete Massiello"
<pmassiello-ml@it
echsol.com> To
Sent by: "'Midrange Systems Technical
midrange-l-bounce Discussion'"
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
cc
10/30/2007 10:39 Subject
AM RE: Capturing job log information
on a text file
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
Well you could build a logical over one QHST file at a time, and only
include the msg-id that is associated with job start and the job end. Then
you would have a file to read and perhaps write out to the IFS, and at the
end of the current QHST file, you would delete the logical file, and create
it over the next QHST file.
Pete Massiello
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Oscar Navas
Sent: Sunday, October 28, 2007 12:26 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Capturing job log information on a text file
Hello.
I had sent the question included herein to be posted on RPG 400 programming
to rpg400-l-owner@xxxxxxxxxxxx; however, it got rejected since the
moderator considered it had nothing to do with RPG programming. Well, since
they advised me to send it to this forum, I am proceeding as suggested and
hope this time around it gets approved for posting. Thank you, in advance.
The message I would like to be posted is as follows:
Hello.
First of all, I am not a programmer, so what I'm looking for is some sort
of
guidance with a project I have.
I know AS/400 from a user/administrative perspective but I have been asked
to come up with a way to export the start and end times of jobs running in
QBATCH subsystem to a flat file that then can be exported to a document
such
as a spreasheet. This is to reflect the times both start, end and the
obtain
the elapsed time for a series of jobs that run in a daily basis.
Since I have no prior programming experience on RPG or COBOL or the sort, I
have no clue on how to do this (well, so maybe someone can start by
recommending me to study programming in this environment but I would like
to
take that approach only if necessary)
I have tools such as the entire IBM ISeries Access for Windows kit (That
comes with a green screen 5250 emulator and Windows Navigator interface)
but
cannot seem to find a way to do that here.
If I could only find a way to capture the start and end times of jobs (from
job log) and export that information to a file, that's basically all I
need.
Any one has any idea? Maybe someone can even refer me to a proper forum.
Thanks a lot for any help.....In advance.
Regards,
Moris
rpg400-l-owner@xxxxxxxxxxxx
--
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.
midrange.com
