How to personalize your iSeries?

In fact, a ton of users have more of iSeries systems under one roof when they are now being more cost effective. More importantly, users want to personalize how iSeries systems look and run to match their needs. However, what do we do to personalize our systems? 

Read the following advice given by Andrew Borts. He is webmaster at United Auto Insurance Group in North Miami, Fla, often a frequent speaker at COMMON and is former president of The Southern National Users Group, an iSeries-AS/400 user group based in Deerfield Beach, Fla.

Firstly, look at the Sign-on Screen. 

Do we need to override the Program/Procedure or the initial Menu? Do we need to change our Current Library? In fact, all of these items aren't necessary on all of our screens. Remember that we always keep it the same on the console. The source for your sign-on screen has been located in QGPL under QDDSSRC for years. 

Always copy the original. See the following edits Andrew Borts has already made:

A. He changed "Sign On" to "Put Something Here". 

B. He commented out the "Program/Procedure" with (4) asterisks (*). In fact, only 1% of users have changed this. What is more, DSPATR(ND) and DSPATR(PR) are added to protect and Andrew Borts did not display the input field. However, the field must be on the display. We do not need to see it or enter anything within them.

C. Same treatment as in the example he gave for B.

Before we signed into the system, communicating is a great idea. When these edits are in place, we can compile the display as we normally would compile a DSPF source type, and perform the following command to take advantage of that sign-on display instead of the one shipped from IBM. What is more, we can use a message file to display different messages for the users that sign in. It's just a display file. Therefore, look at the following.

D. See B 

E. Under no circumstance change the above.

F. He added some elements that are dynamic that could change from a message file called "SIGNONMF" from a message number of SON 1000 (Signon 1000?) 

They come from the two CL commands!

CRTMSGF MSGF(library of your choice/SIGNONMF) TEXT('Sign-on Message File') And to add the message to the file…

ADDMSGD MSGID(SON1000) MSGF(SIGNONMF) MSG('To Contact Help Desk;')

ADDMSGD MSGID(SON1001) MSGF(SIGNONMF) MSG('Tel: 123-456-7890')

ADDMSGD MSGID(SON1002) MSGF(SIGNONMF) MSG('Internal: Extension 1234')

Finally, modify which display we see.

CHGSBSD SBSD(QINTER) SGNDSPF(library of your choice /QDSIGNONNW)

Where QDSIGNONNW is the name of the file edited within his examples.

Now do not edit the QCTL subsystem's Sign-on – nor do you replace the existing QDSIGNON located in QSYS).

Source: search400