Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

wrkjrna and journal receivers to an outfile ?

832 views
Skip to first unread message

iseriesflorida

unread,
Feb 4, 2009, 4:49:58 PM2/4/09
to
Is there an easy way to get the journal receiver information into an
outfile, I tried with this but it will not work.

WRKJRNA JRN(TEST/TESTING) OUTPUT(*OUTFILE) DETAIL(*RCVDIR) OUTFILE
(QTEMP/WRKJRNA)

No dice, all the other ways will not put the journal receiver as a
field that you can query against.

Karl Hanson

unread,
Feb 4, 2009, 6:46:57 PM2/4/09
to

It looks like this API could be used to get that receiver info:
Retrieve Journal Information (QjoRetrieveJournalInformation) API
http://publib.boulder.ibm.com/infocenter/systems/scope/i5os/index.jsp?topic=/apis/QJORJRNI.htm

In particular, see: Key 1 Output Section

Here is an RPG example using a journal API, although perhaps not this one:
http://www-03.ibm.com/systems/i/software/db2/chgjrnstr.html

--
Karl Hanson

bobilc...@gmail.com

unread,
Feb 6, 2009, 3:45:41 AM2/6/09
to

Jonathan Bailey

unread,
Feb 6, 2009, 10:20:13 AM2/6/09
to

I cant select *outfile for output, only *print & I dont even get
DETAIL as a possible option if I F4.
So I would print it then cpysplf :)
Are you having a problem that in generating one file called QTEMP/
WRKJRNA you cannot now create a new one with a different format? If so
delete the 1st one & try again.

Jonathan.

Karl Hanson

unread,
Feb 6, 2009, 11:13:33 AM2/6/09
to

The help for DETAIL(*RCVDIR) says this in part:
*RCVDIR
The printer file will contain the names of the journal
receivers currently associated with the journal. This
entry will also contain some attribute information
about the journal receiver. This value is not valid <<<
with OUTPUT(*OUTFILE). <<<

Using OUTPUT(*PRINT) DETAIL(*RCVDIR) followed by CPYSPLF should work,
but if the data is needed in a program (or, eg input to SQL query), some
logic would probably be needed to skip over page headings, column
headings, etc. Also there is no guarantee the listing format would not
change, eg in a future release. This is why usage of an equivalent API
is encouraged - much effort is given to avoiding incompatible changes to
APIs. Of course, using an API is not as simple as the OUTPUT(*OUTFILE)
CL option.

--
Karl Hanson

iseriesflorida

unread,
Feb 6, 2009, 11:21:32 AM2/6/09
to
> Karl Hanson- Hide quoted text -
>
> - Show quoted text -

I was able to track down the api to get what I needed, I really needed
the 'x' reference between objects/journal/receiver. Does someone have
code example of reading a spooled file.

0 new messages