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



I had already created the physical file, so that command worked when it
could find the correct spool file.

I think I have it working now, at least it's been running for the last
several hours which is longer than it has. I needed to add the CRTDATE
(*LAST) param to the CPYSPLF command. It was defaulting to *ONLY and would
then complain if there was more than one file.

So far the other error I was running into Cpf3343 (duplicate job names
found) hasn't cropped up again, but at least the CPF3340 (duplicate files)
seems to be working.

I am actually a programmer, but RPG isn't somethign I really want to have to
dig into. Java and Cpp are enough, plus all the multitude of scripting
languages I've worked in.

I'm sure there's some better way to be monitoring in genearl (this company
has been using an as400 for years without any kind of sys admin attention)
but have to start somewhere. At least we'll know there are problems before
the users do.

Thanks for all the help, very possible you'll hear from me again. Hope you
don't regret being so friendly!

Steve


On Wed, Nov 26, 2008 at 10:42 AM, <smorrison@xxxxxxxxxxxxxxxxxxx> wrote:

Stephen,

You're very close. Here's my version of your program:

PGM

WRKACTJOB OUTPUT(*PRINT)

DLYJOB DLY(3)

CPYSPLF FILE(QPDSPAJB) TOFILE(STEVE/PRT133) JOB(*) +
SPLNBR(*LAST) CTLCHAR(*FCFC)

ENDPGM

I added the PGM and ENDPGM statements. you'll put parameters on the PGM
line as you develop more complex programs.

I used the CRTPF command to create PRT133 with a record length of 133
bytes (132 for the report plus 1 byte for printer control characters). The
output file must exist before this program will run.

The CPYSPLF uses JOB(*) to specify the current job. This job ID will
change each time you call this with the RMTCMD command. I also specified
the PRTCTL(*FCFC) parameter. This will add spacing commands to your input
file. Read the help about this command to see if this parameter works best
for you.


Steven Morrison
Fidelity Express
903-885-1283 ext. 292




"Stephen Cochran" <stephen.a.cochran.lists@xxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
11/26/2008 09:13 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Subject
Newbie Question






Preface to say that I'm very new to the as400, stronger unix background.

I'm trying to write a small CL program that puts the output of WRKACTJOB
into a PC file so that it can be FTPed off the as400, ideally having the
CL
program executed by the FTP script using RMCD. I have the basics down as
shown below:

WRKACTJOB OUTPUT(*PRINT)

/* Delay for 2 seconds for output to finish */
DLYJOB DLY(3)

/* Copy spool output to file KAF/WAJFILE */
CPYSPLF FILE(QPDSPAJB) TOFILE(KAF/WAJFILE) +
JOB(419900/USER/QPRTJOB) SPLNBR(*LAST)

DLTSPLF FILE(QPDSPAJB) JOB(419900/USER/QPRTJOB)

This will sometimes work, and sometimes not ending with a CPF3343 message.
I
have tried ending a MONMSG line to catch those, but even putting a DLTSPLF
command in the MONMSG ends with the same error.

At this point I've tried just about every combination of options (using
the
job name for JOB parameter, using SMBJOB for the WRKACTJOB command, etc)
but
always run into some problem.

So my question is, what's the correct way to accomplish this? Being
somewhat
new, code examples are always welcome. Thanks.
--
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 Statement: This electronic mail transmission is
confidential, may be privileged and should be read or retained only by the
intended recipient. If you have received this transmission in error,
please notify the sender immediately and delete it from your system.
--
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-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.