Report on Signon and Failed Signon attempts AS400 V5R4


I need to create a audit report for all signon and signoff attempts.

I would like something like

User ID   |    Time/Date   |    IP Address   |   Signon

I have enabled auditing in Go SecTools option 10
Is there an easy way to generate this report?

Thanks, Joe
Who is Participating?
tliottaConnect With a Mentor Commented:
I want to view all accounts that have a failed login attempt againest them...

Assuming that auditing is enabled, failed logon attempts will be logged as journal code 'T' entry type 'PW' in the QAUDJRN journal.

The simplest view of those is with:


A number of parms can be changed to filter results. You might request the *CURRENT receiver instead of the whole current chain, or name specific receivers. Filtering by date/time is possible. For output, you can specify OUTPUT(*PRINT) instead of to the display.

However, the DSPJRNE command has limitations that make it unsuitable for your question. You would need to use the DSPJRN command instead in order to see IP addresses associated with the journal entries.

You can have DSPJRN send its output to a database file. From there, you could run any queries that you needed. For failed logons (T/PW entries), you can experiment with something like this:


Use CRTDUPOBJ to get a copy of the system's model file for PW entries. Then list the PW entries into the file that you just created. A simple RUNQRY command over the file you created will show you what you would have available.

From that starting point, things can go in a number of directions.

As Gary said, you should start with a clear understanding of what is meant by "signon" or "signoff". Logging into a telnet session is a very specific operation. But failed signon attempts will be signaled through any of the servers. Telnet may be a very small part of that.

Further, many "signons" might never show any corresponding "signoffs". It can be tricky trying to determine what constitutes a "signoff" for any given "signon".

Gary PattersonVP Technology / Senior Consultant Commented:

Security auditing isn't really designed to track signon and signoff activities (you can track -failed- logons due to a bad password by querying for PW entries, however).  Chapter 9, Appendix E, and Appendix F explains auditing in detail, including how the audit journals are laid out, how to extract data for reporting, etc.

The "Job Notification Exit Point" (QIBM_QWT_JOBNOTIFY) is probably a better way to get what you want.  You can write a (or buy packaged software) that monitor this exit point and log the data to a database file that you can later query when you need to produce your reports.  THis exit point works a little different from most others, in that you associate a data queue instead of a program.

When a relevant event occurs, and this exit point is enabled, the system will put an entry on the specified data queue.  You would typically write a never-ending program to monitor this queue and write entries out to a database file that you can later query to generate your report, or you could run a scheduled process to empty out the queue from time to time.  This second approach is liable to result in a very large data queue object on a busy system, however.

Here are the doc for this exit point:
Example Data Queue processing programs:
A couple of freeware programs (I haven't used them) that use this exit point to log batch and interactive job activity:

I hate to throw another wrinkle at you, but, can you define what is considered a "signon" or "signoff" for the purpose of this request?  The Job Notify exit point is great for activities that cause a brand new job to be initiated (or ended), like Telnet logon, terminal logon, Host On Demand logon, and STRPASTHR.

It isn't so useful with services that make use of prestart jobs, like the Client Access host server jobs:

Network print server
Remote command and distributed program call server
Central server
Database server
Secure database server
File server
Secure file server
Data queue server
Signon server (unique to servers using sockets communications support)

These server jobs provide users with access to the AS/400 database, the ability to run system commands through various facilities, the ability to access spooled file, and much more.

Other services, such as some of the TCP servers (FTP, for example) also operate in a similar manner.

Even though the user enters a user ID and password to access these services, a new job is often not created.  Instead, the user is attached to and existing pre-started job, and the job's security context is switched to run under the user's profile temporarily.  When the user disconnects of logs off, the job is not terminated - it just switches back to run under a system profile.

So, depending on the purpose of the audit report, you may need to consider tracking logon and logoff to these (and other server-type jobs) facilities.  IBM provides Exit Points for most or all of these servers.  If you need to cover a large number of services, however, you may want to consider purchasing one of the several excellent third-party Exit Point security suites available on the market, which often include robust security audit reporting tools, too:

As you can see, this can quickly grow into a big, complex issue, so you may want to consider bringing in an expert to help the first time you go though implementing AS/400 security auditing and reporting

- Gary Patterson

joe90kaneAuthor Commented:
Hi Gary,

Thank you for the explanation,

For a quick example I want to view all accounts that have a failed login attempt againest them, the Date & time + IP address is available.

Is this easily generated?
Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

Typo "However, the DSPJRNE command..." should be "However, the DSPAUDJRNE command...".

joe90kaneAuthor Commented:
Hi Tom.

This works great 'DSPAUDJRNE ENTTYP(PW) JRNRCV(*CURCHAIN) OUTPUT(*)' but as you asid it doesnt display the time/date or IP address of the users.

I have ran


Im not sure what RUNQRY I need to display the report.
The RUNQRY command was a suggested example of a default kind of "query". After successfully running the above two commands, you should be able to run this command:

== > RUNQRY  *n  MYPW5

A more complete version of the same command is RUNQRY QRYFILE((QTEMP/MYPW5)) but using defaults can sometimes simplify things.

The resulting output will show the various data elements available for each journal entry. Many of the columns will duplicate other rows because they're all the same type of entry. Regardless, knowing what's available is important in order to decide what's needed.

Once the available data is reasonably understood after looking at it, different queries (and different types of queries) can be created to present the data in needed forms. If query assistance is needed, it might be best under a new question since query capabilities can vary widely between systems, depending on options that are installed. Simple queries of the above data is probably easy to fit within this question.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.