Interesting find.

BTW, we use remote outqs to send SPLFs between systems. Very easy & you only have to set it up once. To use, just send change the SPLFs to that outq and the system sends them automatically. It's pretty fast, too.

To create, it's something like CRTOUTQ .. RMTSYS(*INTNETADR or system_name_if_in_dns) RMTPRTQ('library/outqname on remote system') CNNTYPE(*IP) DESTTYPE(*OS400) and add INTNETADR('111.222.333.444') if you used *INTNETADR in RMTSYS. If it requires a manufacturer type/model (I don't remember if it's required), you can use *HP5SI (we've used it with success).

Then STRRMTWTR to start it. Add the STRRMTWTR to QSTRUPPGM to make it persist across IPLs.

Note that remote outqs can also be used to send to other operating systems like AIX (DESTTYPE(*OTHER) .. DESTOPT('XAIX'), Netware, S/390, etc.

John A. Jones, CISSP
Sr. Analyst, Global Information Security
Jones Lang LaSalle, Inc.
Voice: +1.630-455.2787
FAX: +1.312.601.1782
Email: john.jones@xxxxxxxxxx

-----Original Message-----
From: midrange-nontech-bounces@xxxxxxxxxxxx [mailto:midrange-nontech-bounces@xxxxxxxxxxxx] On Behalf Of Tom Liotta
Sent: Thursday, January 08, 2009 8:25 PM
To: midrange-nontech@xxxxxxxxxxxx
Subject: For humor, rather than technical...

I had a bunch of DMPCLPGM splfs on one system, all from the same
job, that I wanted to send to another system. SNDTCPSPLF was the
obvious choice, but I was irritated at having to run the command for
each individual splf. I started going through the parms in detail,
hoping to find some combination of values that would send all of
them at once.

The JOBSYSNAME() parameter caught my eye... I'd never needed it
before, so I hit [F1] to see if it might be useful.

Interesting [help] text. Not necessarily 'helpful', but interesting.

It starts this way:

Job system name (JOBSYSNAME) - Help

Specifies the system from which the job that created the spooled
file was ran on.

I read that a few times, trying to make sure I understood it. Not
being sure, I read farther to see what the special values meant. The
first (the default) is *ONLY:


One spooled file from the job with the specified job name, user
name, job number, spooled file create date and spooled file create
time. If *ONLY is specified and more than one spooled file has the
specified information listed above, an error message is sent.


Well, THAT didn't make it any clearer. So, on to the next one --


The job on the current system with the specified job name, user
name, job number, spooled file create date and spooled file create


Hmmm... still a little vague. The only other listed value is a 'name':


Specify the name of the system where the job ran that created the
spooled file.


Ah! Okay, so the deal is that I _might_ have a bunch of spooled
files on a system, all of which _might_ have come from various other
systems and _might_ have the same job names, users, numbers, create
dates/times, etc., but that would have different originating systems...

Since the [help] was the same on V5R3 as it is on the V6R1 system
that I checked, I take it that this parm is either rarely/never used
or that everyone who uses it understands it easily. Apparently, no
one has complained about it before.

One side element that I noticed is that a bug with DMPCLPGM from ILE
CL has _finally_ been fixed in V6R1. Ever since ILE CL came out, an
extra page-break would be generated after the second header line on
a page. This caused dump output to print on twice as many pages as
were needed.

Good to know that fixes do eventually get made.

Tom Liotta

Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone 253-872-7788 x313
Fax 253-872-7904
This is the Non-Technical Discussion about the AS400 / iSeries (Midrange-NonTech) mailing list
To post a message email: Midrange-NonTech@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: Midrange-NonTech-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This email is for the use of the intended recipient(s) only. If you have
received this email in error, please notify the sender immediately and then
delete it. If you are not the intended recipient, you must not keep, use,
disclose, copy or distribute this email without the author's prior
permission. We have taken precautions to minimize the risk of transmitting
software viruses, but we advise you to carry out your own virus checks on
any attachment to this message. We cannot accept liability for any loss
or damage caused by software viruses. The information contained in this
communication may be confidential and may be subject to the attorney-client
privilege. If you are the intended recipient and you do not wish to receive
similar electronic messages from us in the future then please respond to the
sender to this effect.

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