I was wondering whether there is any way of identifying (in a CL program) the name of the current (attached) Journal Receiver. I know I can do that with WRKJRNA but I cannot use this command in a CL program. The idea is to detach and save the current journal receiver whenever my backup CL runs. We are running on V5R1.
For this answer, I would like to direct you to the vast information found in IBM's Information Center. When first placed online, the Information Center was (to put it politely) difficult to use. But kudos to IBM -- it is now quite usable and quite functional. Go to the Information Center, choose your global location, then choose the OS/400 version you are interested in. In the left-hand navigational pane, open up the Programming topic. Then open up the CL and APIs topic. Choose "APIs by category". The main panel now displays all of the categories of APIs. Choose the Journal and Commit category. Now scroll down to the Retrieve Journal Information API. This API will allow you to programmatically retrieve the currently attached journal receiver.
MORE INFORMATION ON THIS TOPIC
The Best Web Links: Tips, tutorials and more.
Search400.com's targeted search engine: Get relevant information on security.
Ask your systems management questions--or help out your peers by answering them--in our live discussion forums.
Read this Search400.com Featured Topic: Secure your iSeries
Dig Deeper on iSeries system and application security
Related Q&A from Carol Woodbury
Before changing password levels and upgrading operating systems on the AS/400, ensure the clients connecting to the NetServer do not need the old ... Continue Reading
Look in the audit journal (QAUDJRN) on the AS/400 for an authority failure message with the name of the library as the object name. Use the ... Continue Reading
The UPPWEI field corresponds to the password expiration interval field, and its values "0" and "-1" represent the *SYSVAL and *NOXMAX commands. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.