System Operator’s Guide
MaddenCo Inc.
Revised August 2003
Copyright © 2003 by MaddenCo, Inc
All rights reserved.
1
Please understand that MaddenCo has expended substantial sums in developing and maintaining its software, systems and
related materials, and as a result, it has and will continue to have substantial proprietary interest and valuable trade
secrets therein. Also understand that MaddenCo's software, systems, related materials and the "ideas" represented by
software, as well as the physical materials, are valuable trade secrets and are strictly confidential material, and important,
and that its confidentiality gravely affects the successful conduct of the business of MaddenCo.
2
Table of Contents
AS400 .......................................................................................................................... 7
User Profiles ............................................................................................................... 7
Adding a User Profile................................................................................................. 8
Assigning a user profile to a specific menu ................................................................... 9
Keeping a user from Signing onto the System............................................................. 10
Commonly Used Commands ....................................................................................... 12
Cleanup Output Queues........................................................................................... 12
Creating an Archive Output Queue ......................................................................... 12
Using the Clean Output Queues Function................................................................. 13
CLNUPOUTQ Examples ......................................................................................... 15
Delete all spool files more than 60 days old................................................................... 15
Delete everything from the Archive that is over a year old .............................................. 17
Additional Information .......................................................................................... 19
Printer Commands:................................................................................................. 20
WRKWTR – Work with printers ............................................................................. 20
WRKOUTQ – Locate reports for specific printers ...................................................... 21
WRKSPLF – Locate reports for specific users .......................................................... 22
Changing print spool entries: .............................................................................. 23
Viewing a Report without printing:....................................................................... 25
Deleting spool files that you no longer need:......................................................... 28
Other options available for spool files:.................................................................. 28
Other Function keys available for spool files:......................................................... 29
Tape Drive Commands: ........................................................................................... 30
INZTAP – Initializing a Tape ................................................................................. 30
SAVOBJ – Save Objects to Tape............................................................................ 30
SAVLIB – Save a Library to Tape .......................................................................... 30
SAVSAVFDTA – Save a Save File to Tape............................................................... 30
DSPTAP – Display the contents of a Tape ............................................................... 30
RSTOBJ – Restore Objects from a Tape.................................................................. 31
RSTLIB – Restore a Library from Tape ................................................................... 31
System Commands and Functions :........................................................................... 32
WRKSYSVAL – Work with System Values............................................................... 32
Changing the system date .................................................................................. 32
Changing the system time .................................................................................. 33
WRKSYSSTS – Work with System Status ............................................................... 33
Disaster Recovery ................................................................................................ 35
System Save....................................................................................................... 35
Performing a System Save ................................................................................. 35
Job Scheduler ..................................................................................................... 37
Reorganize....................................................................................................... 38
OS400 Release Levels .......................................................................................... 40
AS/400 Logging................................................................................................... 41
What is logging? ............................................................................................... 41
Interactive Job Log............................................................................................ 41
Batch Job Log ................................................................................................... 43
System History Log ........................................................................................... 44
System Messages ................................................................................................ 47
Displaying System Messages .............................................................................. 47
Automatically Answer Messages .......................................................................... 48
Batch Jobs ............................................................................................................... 51
Where do batch jobs go? ......................................................................................... 51
When are batch jobs finished? .................................................................................. 52
3
Where are the reports?............................................................................................ 54
Can’t find a report?................................................................................................. 56
Other report handling features ................................................................................. 56
Hardware and Communication Guidelines ..................................................................... 57
AS/400 ................................................................................................................. 57
Powering Down the System ................................................................................... 57
Power Down the System Without Restarting.......................................................... 57
Power Down the System and IPL to Bring up the AS/400 ........................................ 58
IPL the AS/400 After Powering Down Without Restart............................................. 59
Manual IPL ....................................................................................................... 59
Moving your AS400................................................................................................. 60
Battery Backup ...................................................................................................... 61
Troubleshooting Hardware Problems.......................................................................... 65
AS/400 Down...................................................................................................... 66
Remote Store Down ............................................................................................. 67
Terminal or Printers not Functioning ....................................................................... 68
Ethernet Communications Problems........................................................................ 71
MaddenCo Tire Dealer System ....................................................................................... 73
Help Inquiry ............................................................................................................. 73
Help Inquiry Sections .............................................................................................. 73
Using Help Inquiry .................................................................................................. 75
Printing Help Inquiry ............................................................................................ 78
Online Help Is Available........................................................................................... 78
Turning on New Features ......................................................................................... 80
Looking up Control keys ............................................................................................. 84
Printer Control Keys ................................................................................................ 86
MaddenCo Technical Support ...................................................................................... 90
Getting ready to call Technical Support. ..................................................................... 90
Faxing information to Technical Support .................................................................... 91
Calling Technical Support......................................................................................... 91
Emergencies .......................................................................................................... 92
Connect/Connect – How to Sign MaddenCo onto your AS/400. ...................................... 93
Before Connecting ............................................................................................... 93
Work with Line Configuration Status .................................................................... 93
How to Connect ................................................................................................... 94
Connection Messages ........................................................................................... 94
Tire Dealer System Options and Features...................................................................... 96
Running Multiple Batch Jobs using Multithreading ........................................................ 96
Operations Window................................................................................................. 97
Setting Up the Operations Window ......................................................................... 98
Suggested Options for Operations Window...........................................................100
Command List .................................................................................................101
Program List....................................................................................................101
Warning ............................................................................................................102
Inquiry Window .....................................................................................................102
Warning ............................................................................................................103
Customer Inquiries .............................................................................................104
Product Inquiries ................................................................................................104
Invoice History Inquiries ......................................................................................105
Other Inquiries ...................................................................................................105
Purchase Order Input ..........................................................................................105
Accounts Payable System Inquiries........................................................................106
Retread System Inquiries.....................................................................................106
4
G/L Matrix List ......................................................................................................106
Display Tire System Status .....................................................................................109
Purges .................................................................................................................112
General Guidelines ..............................................................................................112
End of Month ........................................................................................................113
End of Year...........................................................................................................113
Access .................................................................................................................114
System ACCESS .................................................................................................114
Copy a User’s Control Records ...........................................................................114
Store Access Maintenance .................................................................................115
Control File Maintenance ...................................................................................117
System Access Control Maintenance ...................................................................117
Tire System Access ..........................................................................................119
Accounts Payable Access ...................................................................................119
General Ledger Access ......................................................................................120
Daily Update .........................................................................................................122
Preparing to Run an Update .................................................................................122
Authority to Run Daily Update............................................................................122
Control Records for Update................................................................................123
Save Procedure Control Records.........................................................................124
Printer Control Records for Update......................................................................124
Auto Report Control Records for Update ..............................................................125
Reprint Update Reports.....................................................................................125
Tire Dealer System Status Display of Control Records............................................125
Running a Manual Update ....................................................................................125
Automatic Daily Update on Job Scheduler...............................................................127
Running a Job Scheduled Update........................................................................127
Work with Job Scheduled Entries to Hold Update ..................................................128
Work with Job Scheduled Entries to Submit Update Immediately.............................129
Verify Save ........................................................................................................129
Update Reports ..................................................................................................130
Standard update reports ...................................................................................131
Finding Update Reports .....................................................................................131
Update Reports O% Control Record in Operations Window .....................................132
Reprint up to 6 Prior Days of Update Reports .......................................................132
Balancing Update Reports ....................................................................................133
Balancing Accounts Receivable ...........................................................................133
Balancing Sales ...............................................................................................134
Update Error List ................................................................................................135
System Operator’s Log ...........................................................................................136
Purpose of System Operator’s Log.........................................................................136
What to Write in a Log Book .................................................................................136
Security.....................................................................................................................137
Overview ................................................................................................................137
User Profiles ............................................................................................................137
System Values .........................................................................................................139
Custom Menus .........................................................................................................140
Access control records ..............................................................................................140
Operations Window ..................................................................................................141
When Someone Leaves the Company ..........................................................................141
Allowing Access to the System for an Outside User........................................................141
Final Suggestions .....................................................................................................142
5
6
AS400
User Profiles
The very first thing you must do to use the AS400 is set up a User Id and a Password. On
the AS400, you must have a User profile set up in order to be able to do this. Initially,
these profiles are created on your system by the MaddenCo installation staff before the
AS/400 is shipped to you. However, with personnel changes, there will come a time when
you will need to add a new profile or disable a profile for an employee who has left your
company.
To access user profiles, you must be at a command line. If you are signed on the system
with a System Operator user profile, you will automatically be at a command line. If you
are signed on the system and are in a MaddenCo application, you must access the
Operations Window to get a command line. (This will be discussed later in this document.)
From the command line type in the following:
By typing *all after the command, you will be able to work with all the user profiles that
are set up on your system. If there is only one particular user that you would like to work
with, just type in their profile name in place of *all and only that user’s profile will be
displayed.
7
Adding a User Profile
The above is a list of the first nine user profiles in alphabetic order. In our example, a new
system operator has been hired named Mitchell Smith. Mitchell Smith should have the
same authority as Carol Robinson, therefore, a 3 has been placed next to Carol’s user
profile to Copy. This will copy all of Carol’s user profile values into the new profile.
By copying an existing user profile, there are only two lines that need to be changed: User
Profile and Text description. The user’s password will be the same as the user profile
being created. In this case it is Mitchell.
8
There are several fields to note when creating a new profile:
If User Password is set to *USRPRF, the user id will be the new employee’s password.
If Set Password to expire is set to *YES, the new user will be required to enter a new
password when he signs on the system.
By assigning a User class of *SYSOPR, you will grant new users enough IBM system
authority to run most jobs. More than one trusted person should be set to *SECADM,
security administrator. These are users that will have the ability to create and change
user profiles. At lease one user profile must have a user class of *SECOFR. This user
class has service authority and is the highest level of security available on the system.
IBM supplies a QSECOFR user profile with this user class security level. It’s good idea to
change the password on the system supplied id so that only one or two people on your
system can use this sign on.
Assigning a user profile to a specific menu
In some cases you may want users to sign on to a specific menu from within the
MaddenCo Tire Dealer System. In the above example, the user will automatically sign on
to the Tire Dealer Starting Menu. However, you may want an employee who works at the
counter to go directly to the Point of Sale Menu and not be able to access any other menu.
To accomplish this, you would change two parameters on the user profile.
For Initial program to call, you would enter MPOS, which is the Point of Sale Menu. For
Initial Menu enter *signoff. This will cause a user to be automatically signed off the
system if they try to exit their assigned menu.
9
A better way of limiting what menus and options a user can see is by creating your own
menus from within the MaddenCo Tire Dealer System. More information on this can be
found in the Tire System Help Inquiry entry on User Menu Maintenance or in the System
Menu document. Set the Initial program to call to PSTARTUP. Set Initial Menu to
*signoff to force the user off the system if they attempt to leave the custom menu. Set
the Initial Menu parameter to START to allow the user to access other menus.
It is strongly recommended that F6 – Add (on the Work with user profiles screen) not be
used to create user profiles. There are several parameters that MaddenCo has pre-set on
your existing profiles that will not automatically be set when adding a user from scratch.
Keeping a user from Signing onto the System
Let’s say after a week with our company, it has been decided that Mitchell Smith just can’t
handle the job and he has been let go. You have two options available to keep Mitchell
from signing onto your system.
You can modify his user profile and change the Status to *disabled. This will leave his
user profile on your system, but will not let him sign on.
10
Or, you can type 4 next to his user profile and delete it from the system. This can be
difficult if this user ‘owns’ objects (if he has created files in the course of working on the
system). The objects must be assigned to other users before the profile can be deleted.
It is far easier to disable a user.
In no event should you delete objects owned by a user in order to delete the user
profile. Data can be lost. Please call MaddenCo for assistance if you decide to delete a
profile.
11
Commonly Used Commands
Cleanup Output Queues
The Cleanup Output Queues (CLNUPOUTQ) command allows you to archive or delete spool files from the
output queues on the system. When you specify the archive action, spool files are moved to the archive output
queue. When you specify the delete action, spool files are permanently removed from the system.
Creating an Archive Output Queue
If you would like to archive some of your spool files, you will need to first create an output queue to place the
spool files into. You can do this by using the CRTOUTQ command. The following command will create an output
queue called ARCHIVE in library QUSRSYS.
CRTOUTQ OUTQ(QUSRSYS/ARCHIVE)
12
Using the Clean Output Queues Function
To use the Cleanup function, type CLNUPOUTQ on a command line and press F4. You will see the following
screen:
Output Queue – specifies the names and libraries of the output queues you want to include or omit from the
cleanup. You can specify *ALL to include or omit all queues in the cleanup, or you can provide the names of up
to 50 individual output queues to include or omit.
Include or Omit Output Queues – specifies whether the output queues are to be included in or omitted from the
cleanup. *INCLUDE will include them and *OMIT will omit.
User Id – specifies which user or users, whose spool files are to be cleaned. You can specify *ALL for all users,
*CURRENT to clean up only the spool files for the user submitting the command, or type in a User Id for the
individual whose spool files are to be cleaned up.
Retention Days – specifies how long spool files are retained. Only spool files older than the specified number of
days are cleaned up. Valid values are 0 to 366 days.
Delete or Archive Spool Files – determines whether the spool files are deleted or archived. *DELETE will
delete them and *ARCHIVE will move them into the archive out queue.
Archive Output Queue – if you put *ARCHIVE on the previous parameter, you will need to specify the name of
the out queue that you want your spool files moved into. This can be the out queue that we created previously in
this document or can be another out queue that you would like to use for this function. For archiving purposes,
you can only have one out queue that you can use. If you specified *DELETE on the previous parameter, you will
13
still want to key in the name of your archive out queue. This will prevent your archive out queue from being
cleared during the delete function. If you are not using the archive function, key in *NONE for this parameter.
14
CLNUPOUTQ Examples
The following examples will assume that you have created the ARCHIVE output queue.
Delete all spool files more than 60 days old
15
Delete all spool files that are 60 days old except any spool file on PRT05.
16
Delete everything from the Archive that is over a year old
17
Archive reports ran by user DAVISJ that are more than 28 days old.
18
Additional Information
This command could process for a long time depending on the number of out queues you have
and the number of spool files that are retained in each. It is strongly suggested that you submit
this job and not run it interactively if you will be spanning a broad selection.
To keep your spool files cleaned up on a regular basis, you may want to add this function to the
job scheduler. You can access this by typing in WRKJOBSCDE and pressing enter. You can find
information on adding jobs to the scheduler in the System Operators Manual. This can be found on
our web site.
If you would like to review what is in your archive you can do so by typing in:
WRKOUTQ ARCHIVE
If you would like to print something in your archive, just change the spool file over to an out
queue that is associated with a printer. This will however, remove the spool file from the archive.
19
Printer Commands:
WRKWTR – Work with printers
The WRKWTR command is used to manage printers.
From this screen printers can be held, released and more.
Option 5 – Work with printer writer displays a screen containing information about the
status of the printer writer.
20
This view is useful in trouble shooting printer problems.
Option 3 - Hold entries allows you place the printer writer on hold to prevent spooled
reports from printing.
Option 6 – Release entries allows you to release a previously held printer writer for
printing.
Option 7 – Display messages displays any system messages associated with this printer
writer
Option 8 – Work with Output Queues displays reports on a particular print out queue.
This option takes you to the same screen displayed by entering the command WRKOUTQ
printer id.
WRKOUTQ – Locate reports for specific printers
The WRKOUTQ command is used to manage reports on a specific printer that have not
yet printed. By typing WRKOUTQ printer id on the command line and pressing enter,
you will only see the reports available for printing on the specified printer. Substitute the
desired printer name for printer id.
21
There are several powerful options available to handle spooled reports from this screen.
These will be covered in the WRKSPLF section below, since many of the options are the
same.
Note two functions at the bottom of this screen: F20-Writers and F22-Printers.
F20 displays all the writers that are started for this specific outqueue. F22 is equivalent
to the WRKWTR command and displays the Work with Spool Writer Status screen.
WRKSPLF – Locate reports for specific users
The WRKSPLF command is used to manage users reports that have not printed yet. By
typing WRKSPLF on the command line and pressing enter, you will only see the reports
available for the user who is signed on at the terminal where the command was entered.
22
In this example, User Kim is signed on at this workstation. By typing in WRKSPLF and
pressing enter, you will see that there are 2 reports generated by Kim that have not
printed at this time.
To display reports waiting to be printed for a specific user, type WRKSPLF user id.
Changing print spool entries:
There will be times when you will need to change the printer that report is assigned to or
maybe change the number of copies that will need to print. If the report has already
generated and can be found on your WRKSPLF screen, some options for this report can
be modified.
23
Option 2 – Change entries
By placing a 2 next to the report, you will be able to edit some of the options associated
with this report.
The most frequently performed tasks from this screen include changing the forms type,
changing the printer id and changing the number of copies.
For this report, the printer was changed to PL and the number of copies was changed to 2.
If a document needs to be reprinted starting at a page other than the beginning, press
F10. Additional fields at the bottom of the screen appear.
24
Roll the screen.
In the Starting page and/or Ending page fields you can enter the starting page (and
ending page if you desire) for a partial print of the report. This might be useful for a very
long report from which you would like to print only the totals page at the end or if you
wish to reprint the end of your statements because the printer jammed.
You may also change the end status of the report. Normally, spooled output disappears
when it has printed. You may change the Save File parameter to *yes to retain the
report on the print spool after printing. The status of this entry after printing will be
*SAV.
Viewing a Report without printing:
Option 5 – Display entries
On many occasions, you will run a report and just want to view some totals or other
important information, but you really do not want to print the whole report. Any report
created on the AS400 can be viewed if it exists on the WRKSPLF screen.
25
By placing a 5 on the Opt line, you will see a view of what this report would look like if it
had printed. (Note: blank lines are not displayed in the view.)
You will notice that the report is only partially visible on the screen. There are many
options available to take you to different areas of your spool file. By typing the following
on the Control line, you can:
B
– move to the bottom of the report
T
– move to the top of the report
W20 – shift the screen to start at column 20
Enter the desired column number.
26
+5
-5
P10
– move the screen down 5 lines
– move the screen up 5 lines
- move the screen to page 10
Enter the desired page number.
Notice the F19 and F20 functions at the bottom of the screen. These allow you to quickly
shift the screen view left to right to see the remainder of the line.
It is also possible to search the report for a name or phrase by using the Find line.
Enter the word (or a string of words bracketed by ‘single quotes’) on the Find line and
press F16. Remember this will only find an exact match for each character and case.
Most reports show alpha characters as UPPER CASE.
Press F16 -Find. If the characters you typed are located in the spool file, you will
automatically be placed at the first place within the spool file where they are found. If you
press F16 again, you will be taken to the next occurrence.
27
Deleting spool files that you no longer need:
There will be times when you will want to remove spooled reports from your system. A
good example is a report you browse using the Option 5 to display and do not really need
to print.
Option 4 – Delete entries allows you to delete spooled entries. You will be prompted
to confirm this delete by pressing enter.
Other options available for spool files:
Option 3 - Hold entries allows you to retain reports for later review or printing by
changing a report’s status to hold so that it will not print.
Option 6 – Release entries allows you to release any previously held report for printing.
Option 7 – Display messages will display any system messages associated with the
printing of this entry. Typically this will be a forms change or alignment message.
Handling messages will be discussed later in the messages section.
Option 8 - Attributes displays status information about the report.
Option 9 – Work with printing status gives you printing status information about
spooled items currently being printed. Here there are options to display yet more
information and to change the status of the item.
28
Other Function keys available for spool files:
From the WRKSPLF screen, there are several Function keys available:
F3
F10
F11
F18
F17
F22
- will return you to the screen where you originally initiated the
WRKSPLF command
– will display additional attributes about the report
– will display additional attributes about the report
– will take you to the bottom of all of your spool files
– will take you to the top of all of your spool files
– will take you to a screen where you can manage all printers.
This is the same function as the WRKWTR command.
29
Tape Drive Commands:
INZTAP – Initializing a Tape
Before a tape can be used, it must first be initialized. Each time you use a tape, it is a
good idea to initialize it. Failure to initialize tapes will result in longer save times and great
difficulties restoring from the tape, if ever necessary. Note: All information on the tape is
erased when this command is issued.
INZTAP DEV(TC) NEWVOL(IBMIRD) CHECK(*NO) + DENSITY(*CTGTYPE)
CLEAR(*NO)
SAVOBJ – Save Objects to Tape
There will be times when you may want to save an object or a group of objects to a tape.
In the example below, object TMPROD in Library QS36F will be saved to the tape.
SAVOBJ OBJ(TMPROD) LIB(QS36F) DEV(TC)
SAVLIB – Save a Library to Tape
A whole library can be saved to tape by using this command. In the example below, all
objects in Library QS36F will be saved to tape.
SAVLIB LIB(QS36F) DEV(TC)
In the SAVOBJ and SAVLIB commands listed above, the DEV parameter told the system
to save to the tape device. Another option available for the DEV command is *SAVF.
This value causes a condensed copy of the objects to be saved on the system itself in a
save file under a name you provide.
SAVSAVFDTA – Save a Save File to Tape
Use the SAVSAVFDTA command to save objects stored in a save file to a tape. In this
example, the save file XXTM in library QS36F would be saved to tape.
SAVSAVFDTA SAVF(QS36F/XXTM) DEV(TC) VOL(IBMIRD) CLEAR(*NONE)
DSPTAP – Display the contents of a Tape
Use the DSPTAP command to display what has been saved on a tape. A list appears on
your screen showing details about the objects saved. In this example, every object in
every library is displayed.
DSPTAP DEV(TC) DATA(*SAVRST) OUTPUT(*)
If you would like to see a list of just the library names that are on the tape, change the
DATA parameter to (*LABELS).
If you would like to have a printout of what is on the tape, change the OUTPUT parameter
to (*PRINT).
30
The following options should not be used unless you have been specifically instructed to do
so by MaddenCo personnel. Data can be lost if these commands are inappropriately
used.
RSTOBJ – Restore Objects from a Tape
This option will allow you to restore any objects that were saved with the SAVOBJ
command. In the SAVOBJ command above, we saved object TMPROD in library QS36F to
tape. In the example below, we are restoring that object back into library QS36F on the
system. If the object exists there already, it will be replaced with what is on the tape.
RSTOBJ OBJ(TMPROD) SAVLIB(QS36F) DEV(TC) MBROPT(*ALL)
ALWOBJDIF(*ALL)
RSTLIB – Restore a Library from Tape
In the SAVLIB command above, we saved library QS36F to tape. The command to restore
that library is listed below.
Note: If you are restoring more than one library from a tape, be sure to restore them in
the order in which they were saved. If you do not, the tape will process all the way to the
end and then go back and start over before finding what it is restoring. Also, change the
ENDOPT(*leave) so that the tape will not rewind after the first library has been restored.
RSTLIB SAVLIB(QS36F) DEV(TC) ENDOPT(*UNLOAD) MBROPT(*ALL)
ALWOBJDIF(*ALL)
31
System Commands and Functions :
WRKSYSVAL – Work with System Values
During the year, it may become necessary to change certain values controlling the system
date and time (as when Daylight Savings Time takes effect in the Spring.)
Changing the system date
Enter WRKSYSVAL QDATE on the command line.
Enter a 2 to change this system value.
Key in the desired date in the format shown on the screen. If you are attempting to
backdate the system because of end of month problems, please call Technical Support to
32
discuss the ramifications of changing this value. Users on the system at the time this
value is changed must sign off and back on for their session dates to use the new value.
Changing the system time
Enter WRKSYSVAL QTIME on the command line.
Enter a 2 to change this system value.
Enter the correct time using the format shown on the screen.
WRKSYSSTS – Work with System Status
Enter the WRKSYSSTS command to monitor the status of your system.
33
On this screen you can see the number of jobs currently in the system, the average
amount of time the processor was in use and most importantly, information about storage
usage (hard drive capacity and use.)
Notice the upper right hand portion of the screen labeled Auxiliary Storage. The System
ASP represents the total amount of storage capacity on your system. The most important
number on this screen, % system ASP used, represents the amount of storage used. As
this number approaches 100%, performance begins to degrade. Once this number
reaches a warning threshold (usually set to 90%), serious storage condition messages
begin to be sent to the system operator’s message queue. If the situation is not corrected
and the % system ASP used reaches 99.9%, the system will begin to shut down, canceling
jobs and ending subsystems. Finally, the system will IPL in an effort to free space to
function. You should monitor the information on this screen (and your system operator
message queue) to avoid this critical situation.
34
Disaster Recovery
Your processor, peripheral equipment and the data contained on your system represent a
significant investment of time and money. Every effort should be made to safeguard these
valuable assets.
Every device should be shielded from power spikes by a surge protector. Critical
components (the processor, console workstation and remote location modems) should be
plugged into an uninterruptible power supply. (See specific information on attaching such
a device to your AS/400 in our Hardware and Communications Guidelines.)
In the event of a devastating mishap, even though your processor might be lost, having a
current system save and current data would allow you to be ready for business almost as
soon as a replacement system could be obtained. The operating system, device
configurations, user profiles and data can be restored within hours. The prospect of trying
to recover from such a catastrophic event without a current save should be disturbing
enough to insure you will routinely perform system saves and take steps to secure your
nightly saves from the Tire System updates.
These saves should be stored off site in a secure location.
System Save
Having a system save available is very important if your company experiences a disaster.
If for some reason your AS400 were damaged and replacement was necessary, your
amount of down time will depend on the existence and timeliness of a system save. With
this critical information, you can reload User profiles, hardware configurations, licensed
programs, software libraries, data libraries and help text.
A system save should be done after any of the following occur:
•
•
•
•
•
Upgrade of IBM OS/400 Operating system to a new version
Addition of an additional store to the system
Change in hardware configurations
Installation of new MaddenCo release
Passage of time – save a minimum of every 6 months
Performing a System Save
When performing a system save you need to do the following:
1. Sign on the System Console with the QSECOFR user profile. Your system console is
usually named DSP01 or W1.
2. Initialize at lease 3 tapes. (The additional tapes may not be needed but the save is
underway, it’s too late to initialize another tape without canceling the save and
starting over.) Note that *DEVTYPE is used in the command only if using a tape
that matches the density of your tape device. If not using a tape that matches
your tape device, please enter the correct density. Also, system saves run faster if
35
you use tapes the same size as your tape device. The initialize tape command
follows.
INZTAP DEV(TC) NEWVOL(IBMIRD) CHECK(*NO)
DENSITY(*DEVTYPE) CLEAR(*NO)
3. Verify there is no one signed onto the system and no batch jobs are active. You
can do this by typing the following command
WRKUSRJOB USER(*ALL) STATUS(*ACTIVE)
You will need to sign off any users or end any batch jobs that appear whose users
do not start with a Q.
4. End all subsystems by typing:
ENDSBS SBS(*ALL) OPTION(*IMMED)
Note: If subsystems cannot be ended, you are not executing this command from
the system console or you may not be signed on as QSECOFR.
5. Type GO SAVE and then roll the screen until you see Option 21 Entire System.
Take Option 21 on the menu. Fill in the screen as follows:
Tape device . . . . . . . . . . . . . . . . . TC
Prompt for commands . . . . . . . . . N
Check for active files . . . . . .. . . . N
Message queue delivery. . . . . . . *NOTIFY
Start time . . . . . . . . . . . . . .. . ... . *CURRENT
On later OS versions (V4R3N0 or perhaps earlier), there are additional fields; they
require no changes just press enter. The system save will start. Monitor the
screen for the message indicator. If you see “waiting for a reply to message on
message queue QSYSOPR at the bottom of the screen, press Shift and System
Request. A dotted line will appear at the bottom of the screen. Type the number
6 and enter to display the message. You may be instructed to insert another tape.
Do so and respond to the message with a G. Be sure to do F3 to return to the save
job. Failure to return to the save job means no further processing takes place. You
could spend a very long night sitting on the message screen.
Otherwise, informational message telling how many objects or libraries have been
saved will be displayed at the bottom of the screen. If the message indicates that a
certain number of objects were saved and another number of objects were not
saved, the entire system is NOT a good save.
Note: the system save may take four or five hours or more. You may want to get
this underway and come back a bit later to check on messages that may have
appeared.
7.
36
Store your save off-site in a safe place where it can be retrieved quickly
should it be needed.
Job Scheduler
The job scheduler is an IBM function that allows AS/400 users to automatically run jobs at
predetermined times and dates without having to be around to start them in person.
Some tasks you routinely perform that require a dedicated system (no other users signed
on) can be scheduled to run in off hours.
To access the job scheduler, enter WRKJOBSCDE on the command line.
This screen shows a number of scheduled jobs. Notice the Status column. Several of the
jobs are set to run – status is SCD. Several of the jobs are on hold – status is HLD. Held
jobs will not run until they are released.
Notice the available options at the top of the screen. We can display details about a
scheduled job, change values associated with a scheduled job, remove a scheduled job,
hold or release a scheduled job, or submit a job immediately.
At the bottom of the screen there is an F6 – Add function.
We’ll use the reorganize function to illustrate setting up a scheduled job.
37
Reorganize
Any deleted data record in a file occupies space on your system until a reorganize is
performed. A reorganize requires a dedicated system so it is a job that would normally be
run at night or on a weekend when your stores are closed.
The job scheduler can perform the reorganize task for you automatically. Generally, it's a
good idea to set the reorganize to run at a time when no update will run, such as Sunday
evening. If you perform an update on Sunday, then you should set the reorganize to run
after the update is performed. The following steps outline how to set the Reorganize to run
from the job scheduler every Sunday evening at ll:55 PM.
Press F6 to add an entry.
You will need to modify your screen to look like the one above.
Each scheduled job needs a unique name; here we have given this scheduled task the Job
name Reorganize.
Next we added the Command to run value RGZLIBPF LIB(QS36F) .
We indicated that this job is to run with a Frequency of *WEEKLY.
At this point we can identify the day or days of the week this task will run by entering the
Schedule day. Here, our reorganize will run on Sunday - *SUN. You can indicate
additional days by typing a + in the field below *Sun. Additional fields are displayed for
the entry of more day values.
The Schedule time this job is to start was set by entering 23:55:00. Remember the
system uses a 24 hour clock.
38
Press F10 and roll down to the next screen shown below.
For the Reorganize job, modify the parameters on your screen to match the ones above.
There are several important fields on this screen.
The Omit date can be used to prevent processing of the scheduled job on a particular
date. Perhaps you are going to be open for a 24 hour sale one weekend. We do not want
the Reorganize job to run while you are at the store. You can modify this field at any time
to omit the desired date.
The User field can be used to easily track output from job scheduled programs. If we
were running a program that generated reports, we could use a particular used id and later
look for those reports using the WRKSPLF user id command. Be sure to use a valid user
id that has authority to use the function being scheduled. Use the WRKUSRPRF *ALL
command to confirm the user exists. Please refer to the section on ACCESS for details on
granting authority to access and run Tire Dealer System programs.
Finally, enter a meaningful description for this scheduled job in the Text ‘description’
field.
Press enter and your job will be scheduled on the job scheduler.
39
Notice the Next Submit Date column. A glance at this column tells you when a particular
job will next be run (providing the job is not on hold).
If you wish to run a scheduled job immediately, rather than wait for its next scheduled
occurrence, enter 10 in front of the entry. This causes the job to be executed
immediately. Be sure to omit or hold the job on the Job Scheduler if you do not wish it to
run at it’s next regularly scheduled time. Be careful when using this option. A job that
requires a dedicated system will run into problems if other users are signed on.
OS400 Release Levels
OS400 is the operating system that runs your AS400. If you are ever asked your
operating system release level, you can determine the level by entering DSPPTF. The
release level will be displayed on the upper part of the screen with OS cumulative level on
the lower part of the screen in the example below, the installed release is V4R3M0 which
means your system is on Version 4 Release 3 Modification 0.
40
AS/400 Logging
What is logging?
Logging is used to help the system operator find answers. Using logs, the operator can
find when users sign onto the system, who ran a job, when it was run, where it was run
from, if the job had an error, who answered the error, and more. There are four different
logs available on your system. They are: Interactive, Batch, History, and System Error
Log.
Interactive Job Log
The moment you sign on the system an interactive job is started for your workstation.
The system will log informational messages, error messages, and any responses that were
taken to a message for the user that is signed on. Once the user signs off, the log is no
longer available. It is very important to keep a user signed on if they are experiencing
problems and you plan to call MaddenCo for assistance.
To display the Job Log for an interactive job you will need to do the following:
Press the SYSRQ key on your keyboard to access the Operations Window.
Your Operations Window may appear slightly different from the one above. This window is
user defined. We will discuss how to set this up, later in this manual. You will want to
locate the item, which says Work with User Jobs and type 1 on the option line to select.
41
This will take you to the Work with User Jobs screen displayed below:
Interactive jobs are identified under the Type column as INTER. For this example, we will
be displaying the log for user Kim, who is signed onto device KDAED that is noted as the
Job. To display the log, type 5 beside the job that you would like to view.
You will then be presented with the Work with Job screen. From this screen we will need to
take Option 10 to display the actual log.
42
When the Display Job Log Screen appears, press F10 – Display Detailed Messages and
then F18 – Bottom. The screen below will be displayed.
The messages shown above are normal and are informational only. However, if there
were an error or problem, it would be noted here. Notify MaddenCo Support before
answering any messages.
Batch Job Log
A batch job can be initiated by taking an option on a menu. Once the user has proceeded
through the screens associated with the job, the job will then be submitted to batch. This
means that your terminal will now be available to use for other things while the job
processes in the background on the system. To display the log for a batch job, you will
need to take the same options as identified in displaying the job log for an interactive job.
On the Work with User Jobs screen, Batch jobs are identified in the Type column as
Batch.
While viewing jobs in the Work with Active Jobs Screen, you should notify MaddenCo if any
job has MSGW under the column labeled Status. The MSGW Status alerts you to an
error message that needs to be answered. You should contact our Technical Support
Department before answering any messages. If the problem job is ended from the Work
with User Jobs screen, no job log remains to review. This makes problem solving difficult.
Once the Batch job has finished processing, the job log will no longer be available to view.
In some cases, a log will be spooled out to a printer. If the job cancels abnormally, a
spool file will automatically be created so that you can determine what happened. The
MaddenCo application will also spool job logs for some functions on the system.
MaddenCo job logs are informational only and this does not mean that your job ended
abnormally. The Nightly Update job log is an example of this type of log.
43
System History Log
The AS/400 maintains a history log of activity on the AS400. It logs an entry when a user
signs on and off. It also logs the start and stop times of any job initiated on the AS/400.
The AS/400 logs system error messages and any responses taken to those error
messages. It logs hardware failures and much, much, more. This log does not go away
when a user signs off or the job ends. Several days of history logs are kept on your
system and can be viewed at any time. You can view the History log by following these
steps:
Press the SYSRQ key on your keyboard to access the Operations Window.
Your Operations Window may appear slightly different from the one above. This window is
user defined. (Later in this manual we will discuss how to set this up.) You will want to
locate the item which says Command Line and type 1 on the option line to select.
44
From the Command Entry screen, type in DSPLOG and press F4.
If your screen does not look like the one above, chances are you pressed enter and not
F4. If you did not press the F4 key, you will go directly to the history log and will be at
the oldest message that is available. If you pressed F4, you will have the option to narrow
down your selections to specific dates and times. In the example above, the history log for
August 8, 2000 will be displayed from 8 Am to 10 Am.
45
This is an example of the History Log Contents.
46
System Messages
Displaying System Messages
To display system operator messages, press Shift and System Request. Enter 6 on the
dotted line appears at the bottom of the screen. System operator messages may be
displayed from any menu and from within virtually any program.
Types of System Messages
System messages fall into three general categories: informational, problem and general.
Informational messages provide data about the status of the system or user tasks.
Examples of these messages are IPL status messages indicating what steps have been
completed during the initial program load, sign on messages indicating that a user has
signed on the system or messages indicating a job has completed. No response is
necessary.
Problem messages provide alerts to conditions that need to be addressed. Messages
that require a response provide a highlighted line on which to key that reply. Examples of
these messages are communications lines failing or workstation failures. A more serious
47
message might indicate a serious storage condition. Such a situation requires immediate
investigation to determine the cause and how to alleviate it.
General messages are those that may require responses, but are not of a problem
nature. Printer messages are a good example. These messages may require a response,
such as a forms change acknowledgement.
System messages should be monitored on a regular basis throughout the day. Responses
to messages can adversely affect the operation of the system, so care should be taken
that messages are only answered when the outcome is known. In the case of program
error messages, valuable information about the cause of the problem can be lost if the
message is answered prior to obtaining help from MaddenCo. If there is any question
about the effect a response may have, please call for assistance.
Automatically Answer Messages
Some general messages can be automatically answered. Care should be taken to consider
the individual situation so there are no unexpected results. Forms change and alignment
message on printers lend themselves to auto responses if the printer in question is never
loaded with different types of paper. It would be a bad idea to set up an auto response on
a printer that uses 1411 paper and also check forms. An auto response could allow
reports to print on expensive check forms.
To access the System Reply List Entries screen, on the command line type WRKRPYLE.
When ready to add an entry, take note of the previously used sequence numbers. Each
new entry must have a unique number.
48
Press F6 to add an entry.
To add a response for a change forms message, key in the next available sequence
number (increment by 10 – or 100). Enter the data shown above, substituting the desired
forms name and the appropriate printer id in the comparison data field on your system.
Please note that the printer id and forms name should be in UPPER CASE letters. Also note
there are 6 blank spaces after the forms name. The total letters and spaces for the forms
name must total 10, so if you are using longer forms names you will need to reduce the
number of spaces preceding the printer id.
Press enter when finished to store this response.
To add an align forms message response, press F6.
49
To add a response to the alignment message, key in the next available sequence number
(increment by 10 – or 100). Enter the data shown above, substituting the appropriate
printer id on your system.
Please note that the printer id should be in UPPER CASE letters.
Press enter when finished to store this response.
Notice the responses were added to the system reply list that follows.
The next time the system generates a message for one of the message/printer/forms
combinations detailed in the reply list, the system will automatically respond in the manner
you have indicated. The message requires no further action on your part.
50
Batch Jobs
Most report jobs run in ‘batch’. This means the processing takes place outside the control
of an interactive user session.
Where do batch jobs go?
Batch jobs stack up on the job queue, waiting their turn to become active and generate
their printed output or perform other functions. Jobs appear on the job queue (QBATCH)
in chronological order, according to their priority. High priority jobs will come off the
queue and be executed before lower priority jobs.
To display the job queue, on the command line type DSPJOBQ QBATCH.
In this example, there are three jobs waiting on the job queue. All three jobs have the
same priority and so will execute one after another in the order shown. Should a job with
a higher priority be submitted, that job would process before these.
Notice that jobs for specific users can be identified by the name appearing in the User
column.
Jobs may be cancelled from the job queue by typing 4 beside the entry. Jobs can be held
by typing 3 beside the entry. Canceling or holding update jobs can have other
ramifications. If you are unsure of the outcome of your actions, please call for assistance
before using these options.
51
When are batch jobs finished?
When a batch job becomes active, it leaves the job queue and appears on the Work with
Active Jobs screen.
To display active jobs, on the command line type WRKACTJOB.
Active batch jobs are indented beneath the QBATCH subsystem, found under the
Subsystem/Job column. Normally, the two background print jobs, PRTCKDQ and
PRTCKD2, are always active. Any other active batch job will appear here beneath these
jobs.
Notice that jobs for specific users can be identified by the name appearing in the User
column,
Jobs may be canceled from the job queue by typing 4 beside the entry. Jobs may be held
by typing 3 beside the entry. Canceling or holding updates or purges can have
serious consequences. Data can be destroyed. If you are unsure of the outcome of
your actions, please call for assistance before selecting these options.
When a batch job has finished processing, it no longer appears on the Work with Active
Jobs screen. Completed jobs send a message to the user submitting the job.
52
Access user messages by typing DSPMSG on the command line or by pressing Shift and
System Request. A dotted line will appear at the bottom of the screen. Type the
number 4. You may also access messages by taking the Display messages option on
the Operations Window.
53
Where are the reports?
Jobs with printed output send their reports to print queues.
To display reports waiting to be printed that were generated by the current user, on the
command line type WRKSPLF.
To display reports waiting to be printed for a specific user, on the command line type
WRKSPLF user id.
Notice that jobs for specific users can be identified by the name appearing in the User
column.
54
To display reports waiting on a particular print queue, on the command line type
WRKOUTQ printer id.
Again, notice that jobs for specific users can be identified by the name appearing in the
User column.
55
Can’t find a report?
After looking on the print spools and outqueue for missing reports, two possibilities exist:
Most frequently the problem lies not with the spooled report itself, but with the program
generating the report:
The program may have been cancelled – either from the job queue or from the active
jobs screens.
Perhaps the program generating the report is still active, having waited on the job
queue for a long period for its turn to execute. (WRKACTJOB)
There may be an error on the program itself or on a program running before the
report, blocking the job queue. (WRKACTJOB)
(This is frequently the case with errors on the nightly update save. Since this save
runs from the job queue, before any new jobs are processed for the day, an error on
the save job effectively stops the job queue and no batch jobs will run until the
problem is resolved. Typically someone forgot to insert a tape.) This is another
good reason to frequently check system operator messages. (Press Shift and
System Request. A dotted line will appear at the bottom of the screen. Type the
number 6. )
The other possibility is that the report was spooled to the print queue and:
Perhaps the report has printed, possibly attached to a previously printed report that
someone already picked up.
There may be a message on the printer; perhaps indicating a forms change is
needed. (WRKOUTQ printer id.)
There may have been a problem with the printer causing the entry to be lost.
(Turning the printer off causes data to be lost from the printer buffer.)
Other report handling features
Both the WRKOUTQ and WRKSPLF screens offer several powerful options for handling
spooled output. Please refer to the section on System Commands for these features.
56
Hardware and Communication Guidelines
AS/400
Powering Down the System
Occasionally it will be necessary to power the AS/400 down. There are several ways this
can be done and several possible outcomes from this action.
Power Down the System Without Restarting
A planned power outage or approaching storm may make it necessary to power down the
AS/400 without bringing it back up. Use the PWRDWNSYS command but be sure to
press F4 to prompt instead of pressing enter.
The next screen shows how to fill out the PWRDWNSYS command. On the top line for
How to end, type *immed, for Restart after power down type *NO, and for IPL
source enter B.
57
The AS/400 will power down and can be unplugged
Power Down the System and IPL to Bring up the AS/400
In the event you are asked to power down your system and restart it, perhaps to resolve a
lingering communications problem, use the same command PWRDWNSYS and F4. Fill in
the screen as shown below. How to end should be *immed, Restart after power
down should be *yes, and the IPL source should be B. (The IPL source should always
be the B side.)
58
IPL the AS/400 After Powering Down Without Restart
To restart the AS/400 after a previous power down without restarting, simply press the
white button on the face of the processor. An unattended IPL will start and show numbers
changing rapidly in the window on the AS/400. Note: when the system has reached C600
or C900 the numbers may not change as rapidly. After a bit the display will show 01 B.
The system will soon be up and running.
Manual IPL
If you get to work one morning to find all the workstations are down, and the AS/400 is
flashing numbers starting with C, the AS/400 is in the process of an IPL.
If all the workstations are down there is an orange system attention light displayed and a
different set of numbers appear in the window of the processor, it is probably an indication
of a system error. . Normally when the system is up the window will show 01 B N.
Another set of numbers is referred to as SRC codes. Write down what is showing in the
window on the AS/400.
You can attempt a manual IPL to bring the system back up.
59
On the front panel of the processor, locate the up and down arrow keys and the enter key.
Note the difference between the enter key and the white power down button. You may
need to swing open a cover to expose these keys.
Press the arrow up button until 01 appears in the window and press enter.
Press the arrow up button until 02 appears in the window and press enter.
Press the arrow up button until 02 B M shows in the window and press enter.
Press arrow up button until 03 appears in the window and press enter.
The display in the window should begin to display numbers starting with C, which indicates
the AS/400 is doing an IPL. If the SRC code you had written down returns or another SRC
code displays, call IBM for hardware service. Do not try to do an IPL again.
If the IPL does successfully complete, the processor needs to be reset for normal IPLing.
Since the system does an IPL as part of the daily update, it will not come back up from
that IPL if the IPL settings have been left at 01 B M for a manual IPL.
Resetting AS/400 to Normal IPL (01 B N)
To set the AS/400 back to 01 B N for normal IPL, use the arrow keys as follows.
Press arrow up until 01 appears in the window and enter.
Press arrow up until 02 displays in the window and enter.
Press arrow up until 02 B N shows in the window and enter.
Press arrow down until 01 appears in window and enter.
The display should now read 01 B N which means the AS/400 is now ready for a normal
IPL when the system is next powered down.
Moving your AS400
If the AS/400 is to be moved, even an inch, it is important to have a current entire system
save before powering down the system to move it.
Use the PWRDWNSYS command discussed at the beginning of this section to power down
the AS/400 without restart.
60
Battery Backup
A battery backup or Uninterruptable Power Supply (UPS) provides temporary power to
your system during electrical outages. A UPS allows enough time to perform an orderly
shut down of the system.
In addition to the AS/400, the workstation used as the system console and any modems or
routers used to connect remote stores should also be plugged into the UPS.
Several System Values must be set to co-ordinate between the UPS and the AS/400. Your
UPS is designed to give an alarm when it switches to battery power. This should give you
enough time to bring down your AS/400 normally (with the PWRDWNSYS command with
restart set to *No.). This time period should be a few minutes short of the time interval
for which your UPS is rated.
61
To change a system value, key in CHGSYSVAL system value.
To set the delay time, enter QUPSDLYTIM as the system value.
Enter the expected power supply battery time in seconds. In our example, we’ve entered
900 in the New Value field (900 seconds = 15 minutes).
62
In this example, the AS/400 will sense battery backup power for 15 minutes before
starting to power down automatically. Check your UPS manual for the time interval for
your particular model.
You can also have your AS/400 automatically IPL when power is restored.
Type CHGSYSVAL QPWRRSTIPL and press F4.
63
Set system value QPWRRSTIPL to a value of Y.
When you become aware the system is running on the UPS, you should begin to end
nonessential functions. After several minutes, it would be wise to begin having everyone
sign off. It is better to end programs normally so that the files are closed normally than to
have the UPS eventually fail when the battery is drained.
Recovery will be quicker if the programs are ended normally.
64
Troubleshooting Hardware Problems
Maddenco uses two different methods of connecting to the AS/400: using twin axial
cabling or using TCP over Ethernet cables. Hardware requirements for the two methods
are slightly different. The twin axial method uses assigned ports and address that limit the
number of devices you can attach to the AS/400. The Ethernet method has no such limit.
The methods of troubleshooting connectivity problems are slightly different. First, you
need to first know what type of cabling system is being used.
CHECK THE OBVIOUS
Check to be sure equipment is turned on.
Check that cables (both power and communication) are connected and tight. (On twin
axial workstations, if the cursor is in the right corner of the screen, you probably have a
cable problem or an address conflict. If the cursor is in the left corner of the screen
then it is probably not a cable problem.)
CHECK SYSTEM MESSAGES
System operator messages can be checked by pressing Shift and Sysreq. Type 6 on the
dotted line that appears then press enter. See the previous section on System Messages
for more details.
ISOLATE THE PROBLEM
The next step in troubleshooting is to know where the problem exists.
For example, you have a printer that is not printing.
Is this report or invoice going to the right printer?
Are there messages to be answered concerning this print job?
Has the writer been started?
Has the printer been varied on?
Has the terminal that this printer is attached to been working properly?
If this is a remote store, are the rest of the devices attached to the network
operating properly?
Is the AS/400 operating?
There are many useful commands on the AS/400 that will help answer these questions.
65
AS/400 Down
A - Power indicator
B – Power button
C – Processor lights
D – System Attention Indicator
E – Function/Data Window
F - Up and Down Select Buttons
G – Enter Button
Check the front panel of your AS/400. Do you have a green power light? If there is no
light, then the AS/400 is not plugged in or turned on.
Check the Function/Data window. Under normal conditions the window should read 01BN.
If the information in this window is changing, then more then likely the system is in the
process of starting up. Wait until the information stops changing. If the information stops
on 01BN, the AS/400 should soon be operational. If the information in the window stops
on something else, call MaddenCo for help. Keep in mind, the workstation designated as
console must be powered on and attached to the AS/400 for it to come up normally.
66
Remote Store Down
If a remote store is down, first check the status of the line. Use the WRKCFGSTS *LIN
command.
The line and controller should be active. If the status is other than active, you can use
Option 2 to vary off the line. After the Status changes to vary off, use Option 1 to vary
on the line. When you vary off the line description, the controllers and devices under that
line will also vary off. When you vary on the line again, if you have good communication
with the remote store and all devices modems and controllers are operating correctly, the
line description, controller, and devices should become active.
If the line does not become active, you will need to investigate your communication link.
You may have a problem with your line service, modem, controller, router, frad, dds,
cables, etc. Most devices have indicator lights. It is a good idea to note what lights are
normally on for each device. The lights can point to what is the problem. Consider
swapping the equipment to identify the problem.
67
Terminal or Printers not Functioning
Check the Spool Writer status with the WRKWTR command.
By using Option 1 or Option 2, you can start or stop your selected printer. By using
Option 7, you can also see if there are any messages to be answered.
If the printer cannot be started, then you need to check the printer device status, using
the WRKCFGSTS *DEV command.
68
Use Option 2 to vary off the device. If you are using twinaxial cabling, once the Status
has changed to vary off, use Option 1 to vary on the device. The status must change to
vary on pending before the device will reconnect. If you are using Ethernet cabling you
must vary off the device and leave it with a status of vary off before it will reconnect.
For printer problems, work with the attached terminal first; it is usually causing the
connection problem. It is recommended to always power on your printer before turning on
the attached workstation. This is true no matter which cabling system you are using.
If the device you are trying to restart does not function, you should make sure the device
description matches the actual device type using the WRKDEVD command.
69
Use Option 2 to check or change the device description’s port and switch settings to
match the actual device’s port and address. If this is a remote device, the description will
have a local location address instead of port and switch settings.
If you are using Ethernet cabling for the device, you will not have port or switch settings.
For the virtual devices that Ethernet cabling creates, you can delete the device description
and let the system recreate it when it reconnects.
70
Sometimes you may have problems varying off a device. The command WRKACTJOB will
show you the active job associated with a given device.
By using Option 4 and then pressing F4, you can end the active job immediately by
entering *immed for the how to end parameter. Be certain you have the proper job, or
you may be creating more problems.
Ethernet Communications Problems
For systems using a Server with an Ethernet card using a hub for local workstations and a
hub (known as a router) with an attached modem for remote stores, the following tips can
aid in restoring communications.
If no stores are up and all local devices attached to the Ethernet are also down the
problem is probably that the Server on the AS/400 is not started. To start this up, on the
command line enter ENDHOSTSVR *ALL. Enter ENDTCP. Work with the line
descriptions (WRKLIND) and enter 8 beside the line starting with ETH… There should be
a description that describes this as an Ethernet line. Enter STRTCP. Finally, enter
STRHOSTSVR *ALL. The message ‘Host Server daemon jobs unable to communicate
using IPX’ may appear. Do not be concerned – we don’t use this, anyway.
If only remote stores are down, the problem probably lies with the line. To check the line,
you will need the address for the Server. To find this enter GO TCPADM and take Option
1. Take Option 1 on the next screen and make a note of the IP address of the Server.
71
At a remote store, have someone go to the Windows DOS prompt and enter CD
WINDOWS. Enter DIR PING. Enter Ping ip address, substituting the IP address
of the Server from above.
If the remote PC is communicating with the Server, they will get a response ‘reply from IP
address…’. If the PC is not communicating with the Server, they will get a response
‘Request timed out’. Enter E to exit this DOS prompting. You can locate another IP
address for a workstation and try ‘pinging’ that address to determine if the problem is with
the router (maybe so if this second ping doesn’t work either) or the problem lies with a
cable or phone line. If the second ping fails, contact your phone company to test the line.
72
MaddenCo Tire Dealer System
Help Inquiry
Online documentation is located in Help Inquiry. The documents follow the menu outline
and contain overview documents and 'How to' documents listing control keys, calculations
and general information about a report, procedure or work panel.
Where is the Help Inquiry?
It is Option 22 on the MaddenCo Start Menu, which has options for the Tire Dealer
System, AP, GL, etc. The first screen of the help Inquiry is displayed below:
Help Inquiry Sections
There are four sections in the MaddenCo Help text:
New Features – This lists details of the new enhancements to MaddenCo software for the
release level that is identified. Control key information is also included.
73
Help by Menu Option - Documents are categorized as they are on the menus. If there is
an option on a menu that you do not understand, you can find the details by following
through the help text with the same menu options.
Help by Topic – This is a section of detailed information on how to do various functions
from within the Tire Dealer System.
Previous Releases – This section covers enhancements to our software for previous
releases.
74
Using Help Inquiry
After you have located the item for which you are looking, you can type 1 on the option
line and press enter. This will take you to a list of topics on that subject. Above, a 1 was
placed next to Release 2003 Enhancements. After pressing enter, the following screen is
displayed.
75
To view detailed help text associated with a particular topic, key 5 on the option line
beside the desired item.
76
Here we have an example of the help text associated with the Auto post function in cash
Receipts input.
To print detailed help text associated a particular item, type 9 in front of the desired topic.
77
Printing Help Inquiry
Previously the Option 9 - Print was discussed. There is an additional function from within
the core document that will allow you to print help text as well. Within the document,
press F14 to print. Enter the starting and ending page number (or 999 to print to the end
of this document). Note: If this is your first time printing documentation, you may need to
be set up in the system directory. Call Technical Support for help if the first document you
try to print from Help Inquiry does not print.
Online Help Is Available
From within any screen in the MaddenCo Software, you can obtain help about that specific
function. In this example, the Work with Inventory Adjustments option is displayed:
If you move your cursor so that it is not on an input field on the screen, and then press
F13, you will be placed in the help text about Inventory Adjustments in general.
78
In this example, you are seeing the table of contents for this option. You can page down
and see detailed information about this subject.
With the cursor positioned on the Status of input field, you can press F13 and be taken to
the help text for that specific field.
79
As you can see, you now only see the help text that refers to Status. From this screen you
can page through additional help text that is related to Inventory Adjustments.
Turning on New Features
Enhancements for our current release levels are located on the Help Inquiry menu.
80
81
Current Release documents are at the top of the list. A document is created when a new
release level is started. Changes, additions and deletions to the software are noted.
Within the release enhancement list are categories, which list the specifics of an
enhancement. A new control key list is provided for quick reference of control keys added
for each release level.
The entries in the list may be displayed or printed. Your user name must be in the system
directory in order to print a document. This can be checked with the command
WRKDIRE.
82
Each new release entry contains control keys and features included with that entry.
The information about the enhancement should include where the new feature is
performed, any new control keys needed to perform the operation and how to answer the
control key.
Keep in mind that some new features should not be turned on in the middle of the
workday. Any features so restricted should be set up after an update, before new data are
entered.
83
Looking up Control keys
From within Control File Maintenance, an alphabetic lookup by control key is available.
Position your cursor at the “Start At” field and press F4.
To find a specific control key, type in the first character of the control key you are
searching for. In this example, a C was used.
84
After typing in the C and pressing enter, you will be taken to a list of all control keys that
begin with C.
Once you have found the control key that you are searching for, you can type in the page
number listed. You will then be positioned to the control keys on that page.
The whole page cannot be displayed on the screen; therefore you may have to page down
to find the control key that you were searching for.
85
Printer Control Keys
While we’re discussing control keys, we’ll take time to mention several important keys that
affect report printing: 8X11 and 1411. These keys furnish default printer control
information for reports calling for 8 x 11 and 14 x 11 size forms.
These keys may be added for individual users so that reports generated by a specific user
are printed in the desired fashion.
The data screen (added thru Control Maintenance Option F6 -ADD in each module),
appears as follows:
Form name can be set to the desired ID. If you are always routing reports to the same
printer and always using the same paper, you can avoid forms change messages by using
the same forms name for both the 8X11 and 1411 keys.
Characters per inch controls the horizontal spacing of the report. If you wish to print in
condensed print, use 15.
Lines per inch controls the vertical spacing of the report. Standard spacing is 6 or you
may prefer 8.
86
Lines per page refers to the number of vertical lines on the paper you are using. This
should be a multiple of the lines per inch. For example, if you are printing on paper 11
inches long at 8 lines per inch, there are 88 lines on the page.
Last line to print on and Start printing on line both control how much white space
appears on the page. Set these keys to give your report a beginning and ending margin.
Printer id identifies the name of the print device your report will be routed to.
Number of copies to print governs how many copies of the report are to be printed.
Max characters per line refers to how wide the report will print.
Save after printing if answered Y will cause the printed report to be retained on the print
spool with a status of *SAV.
Note: if this feature is used, the number of copies to print parameter is ignored.
Print on Both Sides works best with a network printer and your printer must support the
duplex feature. To print on both sides, use either a Y (print duplex) or T (print duplex and
tumble the pages) depending whether you want to bind the output at the top or sides of
the page. If the printer is attached to a PC or terminal, the duplex commands may be
retranslated and you may not get the results you expected.
You may set these control keys to the same values for printing all reports to a single
printer. If you send wide carriage reports to a different printer, use that printer id and the
appropriate line length.
Be sure to create these keys in each Tire Dealer System module.
87
Error Log
The Tire System Error Log is accessed from the System Menu, Option 7.
All entries are written to this file by procedures performed by various operations in the
system. The Daily Update and the save procedure would be examples of items recorded in
this log. This file should be reviewed after each update to determine whether any
problems exist. An error list is printed if there are any errors during the Daily Update, but
errors are also written to our error log for reviewing later.
The Daily Update will remove all non-critical errors from the file based on the value of
control key ERRORPRG. This control key contains the number of days to keep non-critical
error messages in the error log. Critical errors must be manually deleted using Option 4 Delete.
Critical
These errors indicate critical problems such as an invoice that is out of balance or a vendor
number that is not set up. These records can be deleted using the delete option after they
have been reviewed, using the display option. Removing the error does not indicate
that the problem causing the error is resolved. After reviewing the error, you
should determine what action to take to resolve the problem.
A critical error that has not been displayed cannot be deleted. This forces critical errors to
be reviewed.
88
Warning
These errors indicate warnings such as missing or invalid G/L accounts or a G/L account
number that was substituted as a default account number. These records are purged
periodically by the update function. They can also be removed using the delete option.
Although these errors are only warnings, they should be reviewed to determine if any
action should be taken to avoid similar errors in the future.
Informational
These errors provide information such as an invoice or work order reset status. The date
and time an end of month is performed is written to this file as an informational message.
These records are purged periodically through the update and they can also be removed
using the delete option. Although these entries do not always indicate errors, they should
be reviewed, using the Option 5 – Display before being deleted with Option 4 – Delete.
Each error can be displayed for more information concerning the error. The program that
experienced the error is displayed, along with information about the user signed on and
the date and time.
89
MaddenCo Technical Support
MaddenCo provides assistance with questions and problems pertaining to the Tire System
software as well as the AS/400. There are a number of resources available to our clients,
including help text associated with menu options, the extended Help Inquiry and telephone
assistance thru our Technical Support department.
Specific information on how features of the software function can be found in the Help
inquiry option on the Starting menu.
This feature serves as a quick reference for most software questions. If, after reviewing
these guidelines, you need more information or are unable to find a solution to a problem,
it’s time to call for Technical Support.
Getting ready to call Technical Support.
If calling on a software question (how to set up or utilize a feature), please be sure you
have consulted the online help first. Very often the advice you receive from Technical
Support comes directly from the same documents you already have on your system. You
can save time and long distance charges by seeking help there first.
If calling about a problem, please do a little background checking first so we can make the
most of our time together on the phone. Frequently other users report ‘problems’ that
90
are simply misunderstandings of how a function works. Many times a call could be
avoided by having the person demonstrate the problem. It is often easier to ‘see’ the
problem when you are not directly involved. Often problems disappear when things like
‘show only’ field input is changed. Try the process yourself to demonstrate the problem
also exists when you attempt the same function.
If the problem does persist, gather as much information as you can:
System, menu and option involved
User, workstation and printer ids
Print keys of screens
Copies of reports
Valid data for input
It is usually more efficient to place your call to Technical Support first, rather than fax
information concerning the problem. A short conversation may solve the issue and
eliminate the need for additional information.
In a later section we’ll discuss keeping a system log book to track events that affect your
system. This information is very helpful in discovering events that coincide with a
problem. Very often the clue for the ultimate solution of a problem comes from you.
Faxing information to Technical Support
Send faxes in response to specific requests from Technical Support. When sending a fax,
clearly print your name and your company's name on the fax as well as the person to
whom you are directing the fax. If you have been issued a Technical Support tracking
number, please include this information on the fax.
Calling Technical Support
Give a brief, accurate description of the reason for your call. Calls are prioritized based on
the problem severity and its impact on normal business operations. When your system is
severely impacted by a problem, you will appreciate this method of deciding who is called
first. Our receptionist is not responsible for decisions made as to which calls are returned
first. Please give your name and company name and a phone number where you can be
reached.
If you are calling about a hardware problem, please have the serial numbers for the
equipment. We must have these numbers before assisting you with a hardware problem.
Be advised there will be a charge for assisting with hardware problems on equipment
acquired from outside sources.
When calling back to continue working on a previous problem, please continue working
with the same person and provide the previously assigned Technical Support Tracking
Number. Starting over with a new Technical Support person requires twice as much effort
on your part, can lead to frustration and will not speed the outcome.
91
Emergencies
Defining an emergency can be tricky. Generally, if a problem is severely impacting your
daily operations – it’s an emergency.
MAJOR EMERGENCIES:
AS/400 System Down (Hardware or power outage)
Update problem
Note: This includes A/P or G/L but please be specific.
Remote communication line or store(s) down
All printers on the system or at a store down
Job queue stopped (no reports run)
MINOR EMERGENCIES:
Workstation down or stuck
Error message in option (name the option)
Normal operations are restricted
NON-EMERGENCIES:
Configuring new equipment
Adding a new feature
Operations questions
If you are planning to move workstations and printers around, please call and schedule a
time when we can best help, if you will be needing assistance.
92
Connect/Connect – How to Sign MaddenCo onto your AS/400.
Before Connecting
Before attempting to connect MaddenCo to your system, take a moment to check the
status of the following:
Is the modem to MaddenCo turned on?
Does the phone line need moved from the fax machine?
If a switch is used for connection, is it set right?
Is someone at MaddenCo ready for the connection?
If you have a home line sharing resources with MaddenCo’s line, has the home line been
varied off?
Type the WRKCFGSTS *LIN command on the command line and enter.
Work with Line Configuration Status
If the other line is not varied off, enter 2 beside the line to vary it off and watch
for the Status value to change to Varied off.
93
How to Connect
Sign off your workstation.
Sign on with the user-id CONNECT and the password CONNECT.
.
Your system will attempt to dial MaddenCo three times. If the system fails to connect, do
not attempt to use CONNECT/CONNECT again without assistance from MaddenCo.
Messages may need to be answered, the QSNADS sub-system may need to be ended, and
the MaddenCo line and controller varied off.
When the connection job has started, the screen will go blank for a moment. Then a
message will display. Read the screen carefully for one of the following error or status
messages:
Connection Messages
CPF 2652 – controller description not changed will not prevent MaddenCo from
signing on your AS/400. Take option I to ignore. After entering, the screen will go back
to the sign-on screen and you can resume normal activities.
CPF2640 – vary command not processed will prevent MaddenCo from signing on to
your machine because another controller or line needed by the Connect job has vary on
pending or connect pending status. This status conflict must be resolved before
proceeding. If this error is not solved and you press enter, the connect job will not
process and time will be wasted until we finally start checking for errors. Refer to the
previous section on WRKCFGSTS *LIN and WRKCFGSTS *CTL for the commands to vary
off the conflicting line and controller. If you do not know which line or controller is causing
the conflict, please call MaddenCo.
94
If the message does not contain a CPF message and indicates press enter to
continue, it’s time to press enter. The sign-on screen will appear. Sign onto the system
with your normal user-id and password.
.
Note: if a home line and/or controller was varied off to initiate the connect job, these must
be varied back on after MaddenCo’s session has ended in order to use the line again.
It’s a good idea to be sure someone in addition to the system operator knows how to do
CONNECT/CONNECT, just in case your system operator is not available. Problems
seldom happen at convenient times.
95
Tire Dealer System Options and Features
Running Multiple Batch Jobs using Multithreading
Normally, batch jobs run one at a time. Each job has the same priority, and waits its turn
to exit from the job queue and become active. It is possible to have some batch jobs run
concurrently thru the use of multithreading.
Multithreading assigns different job queue priorities automatically depending on the type of
report being run:
Thread 3 - Customer based reports
Thread 4 - Product based reports
Thread 7 - Sales reports
Thread 8 - Invoice History based reports
Thread 9 – Retread reports and Vehicle reports
Thread 6 is not used by our reports and could be used for your own job queue
management, if you desire.
Thread 5 is the default priority and would be used by all other reports.
For example, this feature allows a sales report, an inventory adjustment edit register and a
reprint of an invoice history register to execute at the same time.
This convenience is not without cost. Overall system response time may degrade if your
system is not configured to handle heavy batch processing demands. (Server models are
well equipped to take advantage of this feature.)
To use this feature, when no users are on the system, set Tire System control key
JOBQPTY to Y.
You should monitor your system‘s performance. If your system bogs down under the
additional processing load, set the JOBQPTY key to N to return to normal threading.
96
Operations Window
The Operations Window is available on any screen in the MaddenCo Tire Dealer System.
This function allows you to do operator functions without exiting from your current
program.
To access this feature, press Sys Req. Depending on your workstation, you might need to
press the Attn or Esc key. In our examples, we’ll use the Sys Req key.
For example, while in Point of Sale you could be entering a sales ticket or estimate. When
you press Sys Req, a window appears with a list of options where you can check the
status of a printer or send a message to another user. When you have completed this
task, you can go right back to the ticket you were working with.
97
Setting Up the Operations Window
Control key O%99 (where 99 is replaced by a number from 1 to now 99) represents the
sequence of commands or programs in the list and contains the name and description for
each option available in the Operations Window.
When presenting the list, the Operations Window first looks for control records by User-ID,
by Work Station, by Store Number and then by system wide inquiries. If you plan to limit
the available operations, the most limited should be by User-ID. If you plan for the
operations to be available to everyone the options should be set up system wide. For
system wide usage, do not define a user, workstation or store. You will want to assign
windows based on your user’s ability, system knowledge and authority.
98
The work panel for Operations Window Control Record entry is formatted. The description
for each option is twenty-five characters long and can be whatever is meaningful to you
and your users. The description entered here appears in the display window list.
Answer the prompt for command or program. A command is generally entered on the
command line. A program is generally executed by a call. When the names are viewed in
the Work with All list, if the name is a command it is preceded by a C; if the name is a
program, it is preceded by a P.
Enter any parameters and their values required for a command. Parameters are available
only for commands, which means only programs without parameters can be setup in the
Operations Window.
The program name or command for each option MUST be correct. Programs and
commands available for use are listed below.
99
Suggested Options for Operations Window
The following operations window options are recommended set up by:
SOU = System operator user ID and backup system operator
WS = Work station ID (Example: Point of Sale work stations)
SW = System Wide (For all users on system.)
See next page for other commands or programs available.
Description
Command Line
Cmd
or
Pgm
P
Program
Command Parms
QCMD
SOU
WS
Or
SW
S
O
U
SW
SOU
SOU
SOU
Note/Memo Pad
Job Scheduler
Update Reports
6 Days of Update
Reports
Print Spool
Invoice Printer
Work Order Printer
All Printers
Job Queue
Active User Jobs
P
C
C
C
PSYUSRMM
WRKJOBSCDE
WRKSPLF
WRKOUTQ
C
C
C
C
C
C
WRKSPLF
WRKSPLF
WRKSPLF
WRKWTR
WRKJOBQ
WRKUSRJOB
Batch User Jobs
C
WRKUSRJOB
Work With Active
Jobs
Send Message
Print Message to
Store
WS and User
Messages
System Message
Line Configuration
Status
Controller Config
Status
System Status
Device Status
Time Change
Your Active Log
Forms/Align
Messages
Change Your
Password
C
WRKACTJOB
P
P
QEZSNDMG
PTSNDMS0
SW
SOU
C
DSPMSG
SW
C
C
DSPMSG
WRKCFGSTS
MSGQ(QSYSOPR)
CFGTYPE(*LIN)
SOU
SOU
C
WRKCFGSTS
CFGTYPE(*CTL)
SOU
C
C
C
C
C
WRKSYSSTS
WRKDEVD
WRKSYSVAL
DSPJOBLOG
WRKRPYLE
QHOUR
SOU
SOU
SOU
SW
SOU
C
CHGPWD
100
SELECT (UPDATE)
OUTQ(*LIBL/QEZDEBUG)
SELECT (*ALL P2)
SELECT (*ALL P3)
JOBQ(QBATCH)
USER(*ALL) STATUS(*ACTIVE)
JOBTYPE(*INTERACT)
USER(*ALL) STATUS(*ACTIVE)
JOBTYPE(*BATCH)
SEQ(*CPUPCT)
SW
WS
WS
SOU
SOU
SOU
SOU
SOU
SW
Command List
DSPMSG - Displays messages from system functions or other users.
WRKACTJOB - Work with Active Jobs shows jobs that are active on the system.
WRKSPLF – Display User’s spool file. Displays a list of spooled reports. Allows them to
be viewed and to change certain parameters like the number of copies to print or to delete
these reports.
?WRKSPLF - Prompted Display spool file. Prompts for the user id or printer id to view.
WRKWTR - Work with Spool Writers. This will display a list of all printers and allow you to
start and stop them. Also you can display and answer any outstanding messages related
to each printer.
WRKJOBQ - Work with jobs to be run. Displays all Job Queues. You will be able to
delete, hold, release, or change any job waiting to be run. On the command parms line,
enter JOBQ(QBATCH) to see just the job queue.
WRKUSRJOB - Work with users jobs. Displays the status of user jobs. On the command
parms line, enter USER(*ALL) STATUS(*ACTIVE).
WRKSBSJOB - Work with subsystem jobs. On the command parms line, enter
SBS(QBATCH) to work with batch jobs. Enter SBS(QINTER) to work with interactive jobs.
WRKSYSSTS – Work with System Status shows system information such as % CPU used.
WRKDSKSTS – Work with Disk Status shows size and percent used for disks.
CHGPWD – Change your sign on password.
Program List
*NONE - Ignores putting the entry on the Operations Window list. This entry might be
used to remove a system wide function from a user, terminal, or store.
QCMD - Provides a command line to enter commands.
WHPHDIQ - Help Inquiry calls the main screen help inquiry feature.
PTPSAWKA - Credit Authorization calls a work with all credit authorizations work panel.
Note: You can put this program in the Operations Window and allow users to view credit
requests but they will need access to authorize credit. (The option to edit is not available
unless access is granted).
PTPSAPRW - Price Authorization calls a work with all price authorizations work panel.
PTEHCLCK - Work with Employee Time Clock. This work panel allows employees to clock
in and out. No parameters are required.
101
PTFMHWK – Work with Printable Forms. This work panel allows special forms or
documents to entered to print at a later time when they are needed. These can be
company policy or disclaimers for customers.
QEZSNDMG - Send a display message will allow you to send a message to any user on
the system. The message can be sent to one, several or all users. If you do not know a
user's ID, you can get a list of all valid users from this display. The message can be sent
to interrupt the receiver and can require an answer.
PTSNDMS0 - Send Printed Message to Store (s). This program sends a written message
to the store or store numbers entered in the store selection work panel. Printer control
key INVC is used to determine the printer id to use to print the message.
PSYUSRMM - User Memo Pad. This is an entry program to make notes for a user id. The
memo system work panel is used for entry but other memos are not accessible
when the user notes program is being used.
Warning
Calling the same program from a menu and from the Operations Window at the same time
may cause your terminal to lock. It is best not to attempt this, as the results may be
unpredictable.
Inquiry Window
The INQUIRY option available from within input programs will pop-up a window which will
allow you to choose from up to twenty user defined inquiries.
102
The inquiries can be executed without ever leaving the current process.
The inquiries available in the Inquiry Window can be defined by User-ID, by WorkStation,
by Store Number, or system wide. When presenting the available inquiries, the Inquiry
Window first looks for control records by User-ID, by Work Station, by Store Number, and
finally by system wide inquiries. Therefore, if you plan to limit the available inquiries, the
most limited inquiries should be by User-ID. If you plan for the inquiries to be available to
everyone, they should be system wide.
Warning
Be aware that all (most) functions available in an inquiry will also be available to an inquiry
called from the Inquiry Window. For example: The Invoice History Inquiry has an option
to allow an invoice to be reprinted by merely pressing a function key. If you set up the
Inquiry Window and enable Invoice History Inquiry through this feature, you will be able to
reprint an invoice from the Inquiry Window. Realize that persons at Point of Sale will be
able to reprint invoices from invoice history at the counter.
103
Control record Q%99 (where 99 is replaced by a number from one to twenty that
represents the sequence of inquiries in the list) contains the description and program
name for each inquiry available in the Inquiry Window. The description for each inquiry
option is thirty characters long and can be whatever is meaningful to you and your users.
Each control key can be defined by User-Id, WorkStation or Store. For system wide usage,
do not define a user, workstation or store.
The program name for each inquiry option MUST be correct. During setup, you will be
prompted for the program name. The appropriate systems must be installed in order to
use an inquiry program for that system. For example, including a Retread inquiry will not
be successfully, if you do not have the Retread System installed.
Customer Inquiries
WTARIQBL – This is the name of the Customer Balance Inquiry. Open balance and A/R
status inquiry are available from this option. Customer Credit History is available from this
program if Credit Management is installed. You will need access to use some of these
features.
WTCSTIQS – This is a Customer Inquiry by Customer Number.
WTARIQAG – This is an A/R Aging inquiry.
WTSLIQCS – This is the Customer Sales inquiry.
Product Inquiries
WTPRDIQS - This is Product Inquiry by Product Number.
104
WTPDIQ – This is a Product Size or Number Inquiry. This is the inquiry used in POS.
WTPHSTIQ – This is the Product History inquiry.
WTPDIQAV – This is the product availability inquiry.
Invoice History Inquiries
WTIHWKAI – This is the Invoice History inquiry by Invoice number. This program will
use the store you are currently accessing.
PTIHWKAI – This is the Invoice History inquiry by Invoice number, but the program will
ask for store number again. If you have authority, you may enter store zero.
WTIHWKAR – This is the Invoice History inquiry by Reference number. This program will
use the store you are currently accessing.
PTIHWKAR – This is the Invoice History inquiry by Reference number, but the program
will ask for store number again. If you have authority you may enter store zero.
WTIHWKCT – This is the Invoice History inquiry by Contract number. This program will
use the store you are currently accessing.
PTIHWKCT – This is the Invoice History inquiry by Contract number but the program will
ask for store number again. If you have authority you may enter store zero.
Other Inquiries
WTSRNIQ – This is the name of the Serial Number inquiry.
WTPSHIQO – This is the name of the Order Inquiry in Warehouse Order Entry.
WTPSTWKA – This is the Store Sales Total Inquiry.
PTFGMFGI – This is the name of the Tire Guide in Point of Sale.
WTDISWKA - This is the name of the Customer Discount inquiry.
WTSMMWKO - This is the name of Salesman Memo inquiry.
Purchase Order Input
TTMPOHD – This is the name of the Purchase Order Header entry screen. Setup this function in
the Inquiry Window for use in Point of Sale and Order Entry. Then you may create a purchase
order without exiting the current programs in POS and OE.
105
Accounts Payable System Inquiries
PPVNNMIQ - This is the name of the Vendor Inquiry. The last view used for this inquiry
is presented first. The change view function is available to toggle between the vendor
address and phone number. If you do not have access to vendor maintenance in the A/P
control file, a select is the only option available from the inquiry function. The select
option will return to the inquiry window only. If you have access to vendor maintenance,
all options (edit, copy, delete) are available for use through the inquiry.
WPVNSTIQ – This is the name of the Vendor Status Inquiry
WPVNSIQD – This is the name of the Vendor Status Inquiry by Invoice Date
WPGLDSIQ – This is the name of the G/L Distribution Inquiry
WPCHKNIQ – This is the name of the A/P Check Number Inquiry
Retread System Inquiries
Once the inquiry program is executed, the store input screen is presented. A store
number can be input regardless of store access for the Retread System, however, work
order number entry or entry of a customer number that is not valid for that store number
will cause an error message.
WWOINQ05 – This is the name of the Retread Work Order inquiry.
WWOBILRF – This is the name of the Retread Work Order by Billing Reference
Number inquiry.
WWOBRAND – This is the name of the Retread Work Order by Brand Number inquiry.
WWOSRIAL – This is the name of the Retread Work Order by Serial Number inquiry.
WCINQ22I – This is the name of the Retread Rejection Analysis inquiry.
WWOBARCD – This is the name of the Retread Bar Code inquiry.
G/L Matrix List
This report was designed to be a quick reference to the G/L accounts receiving postings
from Tire System transactions. It is also useful for adding a new product class or checking
current product classes. This report is located on the Other Options Menu from the More
Options Menu of the Tire Dealer System Menu.
This report will list all product classes in your Tire Dealer System Control File. The product
class, class description, and the G/L account number this class will post to when a sale is
made to each of the possible ten customer classes will be listed. Also, if this class is
excluded from sales totals, has forced sales or a G/L cost percent, this will be noted in that
column for each product class. Products with G/L overrides from the product file are
listed at the bottom of the report.
106
This report prints using the 1411 printer control key and can also be emailed. See email
setup for more information on emailing reports.
MADDENCO TIRES
Job ID: 09/07/0011:30:28CRSUP
User: CAROL
Pgm: RTGLPMRP
Sys Time: 11:30:33 09/07/00
1
DATE 09/07/00
Store Number: 000
G/L POSTING MATRIX LIST
Page:
(SLEX099)(COST%99)(SLCGS99)(GLCGS99)*
EXCLUDED
FORCED
FORCED
(GLSL998)**
(PCLS099)*
FROM
SALES
G/L
|--------------- G/L SALES ACCOUNT BY CUSTOMER CLASS ----------------|
PRODUCT CLASS
SALES
COST%
COST%
0
1
2
3
4
5
6
7
8
9
01 ADJUSTMENT & CREDIT
00000 00431 00432 00433 00434 00435 00436 00437 00000 00000
02 LIGHT TRUCK TIRES
00400 00400 00400 00400 00400 00400 00400 00400 00400 00400
05 PASSENGER TIRE
00000 00411 00412 00413 00414 00415 00416 00417 00000 00000
06 MOTORCYCLE TIRES
00411 00412 00413 00414 00415 00416 00417
10 MEDIUM TRUCK TIRES
00411 00412 00413 00414 00415 00416 00417
16 SOLIDS
00411 00412 00413 00414 00415 00416 00417
20 INDUSTRIALS
00411 00412 00413 00414 00415 00416 00417
25 GRADER TIRES (HEAVY EQ)
00411 00412 00413 00414 00415 00416 00417
29 OFF ROAD
00411 00412 00413 00414 00415 00416 00417
30 RIB IMPLIMENT
00411 00412 00413 00414 00415 00416 00417
32 TRACTOR FRONTS
00411 00412 00413 00414 00415 00416 00417
35 TRACTOR REARS
00411 00412 00413 00414 00415 00416 00417
45 TUBES
00411 00412 00413 00414 00415 00416 00417
48 VALVES AND WEIGHTS
00431 00432 00433 00434 00435 00436 00437
49 WHEELS
00431 00432 00433 00434 00435 00436 00437
50 MAG WHEELS
00431 00432 00433 00434 00435 00436 00437
51 MAG ACCESSORIES
00431 00432 00433 00434 00435 00436 00437
52 SPRINGS AND SPACERS
00431 00432 00433 00434 00435 00436 00437
53 STUDS AND CHAINS
00431 00432 00433 00434 00435 00436 00437
54 HUBS
010
00431 00432 00433 00434 00435 00436 00437
60 SHOCKS
00431 00432 00433 00434 00435 00436 00437
61 BATTERIES
00431 00432 00433 00434 00435 00436 00437
62 FILTERS
00431 00432 00433 00434 00435 00436 00437
64 PARTS (BRAKES & MUFFLER)
00431 00432 00433 00434 00435 00436 00437
65 LABOR SERVICE
00000
00421 00422 00423 00424 00425 00426 00427
67 EXTENDER WARRANTY
00431 00432 00433 00434 00435 00436 00437
68 FILL (TIRE FLUID)
00431 00432 00433 00434 00435 00436 00437
80 RETREADS
00411 00412 00413 00414 00415 00416 00417
81 CASINGS
00411 00412 00413 00414 00415 00416 00417
DATE 09/07/00
G/L POSTING MATRIX LIST
Page:
2
(SLEX099)(COST%99)(SLCGS99)(GLCGS99)*
EXCLUDED
FORCED
FORCED
(GLSL998)**
(PCLS099)*
FROM
SALES
G/L
|--------------- G/L SALES ACCOUNT BY CUSTOMER CLASS ----------------|
PRODUCT CLASS
SALES
COST%
COST%
0
1
2
3
4
5
6
7
8
9
82 RETREAD REPAIR
00000
00421 00422 00423 00424 00425 00426 00427
98 DISCOUNTS
00000
00431 00432 00433 00434 00435 00436 00437
99 TAXES
Y
00000
00431 00432 00433 00434 00435 00436 00437
* Control Keys
* 99 = Product Class
Add 00100 to the above numbers to get the corresponding
** 99 = Product Class
8 = Customer Class
Cost Of Goods Sold G/L Account Numbers (CSGADDR)
107
Below is a list and description of control keys that are read for this report. The control
keys for each column are listed in the heading.
CGSADDR - contains the number, which is added to the General Ledger account
number for sales, determined by product class code and customer class code, to get the
General Ledger account number for Cost of Goods Sold entries.
GLCGS99 - where 99 is a product class, contains Cost of Goods Sold percentage for a
particular product class code. This percentage is used instead of the actual cost in the
Cost of Goods Sold calculations. If a GLCGS99 key is set up for the customer class
being processed, that percentage will be used. If there is not a GLCGS99 key for this
customer class, the control file will be read to determine if there is a customer
class/product class key, GLCGS899 for this customer and product class and if so, that
percentage is used. If neither of the new keys is set up, the original GLCGS99 by
product class key will be read for this product class and that percentage will be used for
this calculation.
GLPOSTUN - contains a Y or N indicating whether sales units will be posted to a 'Units'
account in G/L. If answered Y, sales units will be posted to the units account
maintained by control key GLSU889 (where 88 is the product class and 9 is the
customer class.)
GLSL889 - where 88 is a product class code and 9 is a customer class code, contains
the General Ledger account number for sales (income) entries for a particular product
class code and customer class code.
PCLS099 - where 99 is a product class code. Contains the product class description for
this product class code.
SLCGS99 - contains the Cost of Goods Sold factor, which is used to calculate the new
replacement cost and actual cost for a particular product class. The factor is used in the
following manner: SALES AMOUNT * THE FACTOR AMOUNT = COST OF GOODS SOLD.
To specify this percentage by customer class and product class use SLCGS899 or by
customer class, use SLCGS9. If a SLCGS9 key is set up for the customer class being
processed, that percentage will be used. If there is no SLCGS9 key for this customer
class, the control file will be read to determine if there is a customer class/product class
key (SLCGS899) for this customer and product class. If a key exists, the key value is
used as a percentage. If neither of the new keys is set up, the original SLCGS9 by
product class key will be read for this product class and that percentage will be used for
this calculation.
SLEX999 - where 999 is a product class code. Contains a Y or an N indicating whether
products with this class code are non-merchandise products, which are excluded on the
sales and sales tax reports.
108
Display Tire System Status
This work panel lists the current status of the Daily Update, your current release level
and other information concerning the update process.
The first entry in the list indicates the current release level of your system. The PTF
creation date and the date the PTF was installed on your system are displayed. This
information is updated by the PTF process.
109
Each entry represents the value of a control key associated with the update. By using
the display option, the status of an update operation, the associated control key, the
current value of the control key, the last date and time the control key was changed by
the update and the user that initiated the job are displayed. You cannot change the
value of the control key. It is only displayed for information purposes.
Descriptions of the entries are listed below.
Tire Dealer Update
This entry indicates the current update status. The value of control key UPDATING is
displayed. The status of the last update program and the program name that caused
the status is listed along with the date and time of occurrence. This control key is
maintained by the update and the value should not be changed.
Balance Cash Drawers
This entry reads control key BALNCING for the status of stores that are currently
balancing their cash drawers. This is helpful in seeing which stores have not closed out
their cash drawers for the day. The last date and time the cash drawers were balanced
is displayed along with the user id and the workstation where the balancing was
performed. This control key is maintained by the update and the value should not be
changed.
110
Save Procedure
This entry reads control key USERSAV and indicates whether you are using a custom
save procedure in the daily update procedure or the standard MaddenCo save
procedure. If this control key is answered Y, you should have a custom save procedure
in your custom library. If this key is answered N, control key DISKSAVE is read to
determine whether to save your data files to a save file on disk during the daily update.
After a successful save, you may then save these files to an external save media
yourself or have the update automatically save the files to an external save media by
answering control key SAVSAVFL with a Y and SAVMEDM with your save media/device
ID. If DISKSAVE is answered N and you are not using a customized save, your files
will be saved directly to the save media specified in control key SAVMEDM. If you are
using tape cartridges, control key SAVTAPDN contains the tape density to be used to
initialize your tapes.
Save Update Reports
This entry reads control key UPRPTSAV and determines whether the update will save a
copy of the update reports to the QEZDEBUG job log. This option can be used during
initial updates to ensure that the update reports can be reprinted if needed.
Other Entries
Other entries indicate the operations that are performed in the Daily Update.
Point of Sale invoices will update automatically in the nightly update if control key
POSUPDT is answered Y.
Retread work orders will update automatically during the nightly update if control key
@UPDRTD is answered Y.
Warehouse Order Entry invoices will update during the nightly update if control key
ORDUPDT is answered Y.
Daily Sales will be updated during the nightly update if control key SLSUPDT is
answered Y.
Purchase orders will be updated during the nightly update if control key POUPDT is
answered Y.
National Account Billing will be updated during the nightly update if control key
NABUPDT is answered Y.
Answer control key PASTDUE to indicate whether you want each customer checked for
past due invoices during the A/R and inventory update. If answered Y, customers are
checked.
Answer control key PRCAPUP with Y to automatically apply product pricing from the
price file to products during the Daily Update.
Answer control key APUPDT with Y in order to perform the Accounts Payable update as
part of the Tire Dealer System Update.
111
Answer control key GLUPDT with Y in order to perform the General Ledger update as
part of the Tire Dealer System Update.
Answer control key EOMAUTO with Y in order to perform the End of Month procedure
automatically during the last daily update of the month.
Answer control key EOMAUTR with Y in order to perform the Revolving Charge End of
Month procedure automatically during the last daily update of the month.
Answer control key AUTORPYN with Y in order to run auto reports and print them
during the nightly update. Control key UPOFAUTO indicates whether the system will
be available before or after the auto reports finish. If answered Y, the system is
available before the auto reports have finished. If answered N, the system is available
after the auto reports have finished.
Purges
Purging on a regular basis keeps the system running at maximum performance. As
data is entered into a system, the files containing this data will grow in size. With
cumbersome files, the system will run slower. To keep the system running its best, we
recommend purging files of old data on a regular basis. This will create room for new
data.
Although purges can be run at any time during the month, we recommend they be
executed at month end. The accounts payable purge should be done after all data from
the previous month is entered and updated, but before the data for the next month is
entered.
Purges may require a dedicated system and they will run from the job queue.
General Guidelines
Error Message - If an error message is displayed during a purge, do not cancel the
purge.
IF YOU GET AN ERROR MESSAGE DURING A PURGE, CALL TECHNICAL SUPPORT.
DO NOT TAKE *ANY* OPTIONS. DO NOT CONTINUE!!
File Save - It is very important to save the files being purged BEFORE the purge is
performed.
Date Selection - Entering the correct date when purging files is very important. The
purge removes records dated prior to and including the date entered. If today's date is
entered, everything in that file dated up to the current day will be removed. Doublecheck the screen before continuing.
112
End of Month
Completing end of month steps for each system package will provide you with periodic
pictures of your system. Some of our modules have reports that print month to date
totals for you. Running the end of month option will zero those totals to prepare you for
the next month. By neglecting end of month procedures, these reports become
inaccurate thus handicapping your ability to know your company's current status.
The End of Month process is logged to the System Error Log file as an information
message, indicating when the end of month was performed.
You will need access in order to perform this procedure.
Please refer to the document on Month End for specific details.
End of Year
This option allows you to zero out year to date information in your files. The execution
date for the end of year is logged to the System Error Log as an informational message.
You will need access in order to perform this procedure.
Please refer to the document on Year End for specific details.
113
Access
Entry to the Tire Dealer System functions can be controlled by the ACCESS feature.
There are several levels of access to be granted when setting up a new user or when
granting an existing user more authority.
System ACCESS
At the outset, users must be granted access to the MaddenCo Tire Dealer System
modules for each store they use. This access is granted from the System Menu.
Copy a User’s Control Records
If a new user is being added to the system, the easiest way to set up access records is
by taking the System Menu option to Copy a User’s Control Records.
This function allows you to copy all of one users access and authority for the Tire Dealer
System programs and assign them to another user. This is very useful when adding a
new employee. By using this feature, you can grant consistent access for users
performing the same types of work.
While access records are being copied, a screen appears asking if you wish to copy store
access records. If you want the new employee to have access to the same stores
accessed by the existing employee, answer this question with a Y. See the section
below for more details on Store Access.
114
Store Access Maintenance
If you used the System menu option to Copy a User’s Control Records for a new user,
Store Access records will already exist for that user.
You may need to grant additional store access to an existing employee who was,
perhaps, transferred to another store. From the System menu, take the option for
Store Maintenance, then the Work with Store Access option.
115
Notice that user Greg has access to A/P and G/L for several stores, but he does not
have access to the Tire System. To add access to a system or store, press F6 – Add
Access to a Store/Region.
Now we can assign access to Greg at store 008 for the Tire Dealer System. If you are
unsure of the data code for the system, an F4 prompt is available.
116
Control File Maintenance
If you need to change access (granting or removing authority to perform certain tasks)
for an existing user, maintenance can be done to that user’s ACCESS control record in
each system (Tire System, G/L and A/P). The screens below show the maintenance
screen for each Tire Dealer System module.
Access to functions is permitted by default. If you want to prevent someone from
performing a certain task, you can create an access record for them and answer the
appropriate function with an N. For example, you have 50 users on the system and
only want to permit one of them to run purges in the Tire System. You would need to
set up 49 ACCESS keys in the Tire System (one for each user) with an N in the purge
field to prevent these users from accessing the function. An easier way to do this is
with the ACCESEXP control key. When answered with a Y, this key only allows access
to functions for users whose ACCESS keys exist and have a Y beside the attempted
function. Using this feature can considerably reduce maintenance time.
CAUTION: If you decide to use the ACCESEXP function, make certain you have
granted access to several users (including MaddenCo). If Access is not granted for
control file maintenance in the Tire System, you could find yourself without access to
any function and no way to change the situation.
Remember to set up a user’s ACCESS control key in each Tire Dealer System module a
user will be allowed to get into. If you used the Copy a User’s Control Records option
on the System menu, these records have already been created.
System Access Control Maintenance
To add or change access for users responsible for system operations, take the option for
System Control File Maintenance from the System Menu.
117
From this screen, ACCESS keys can be displayed with Option 5, edited with Option 2,
deleted with Option 4, and copied with Option 3.
Notice the F6 – Add function at the bottom of the screen. Use this function to add new
system operators to the system. Only employees responsible for system tasks such as
the update should be added in the System Control file ACCESS records.
Our example below shows an ACCESS record for user Donna that is being edited.
118
Help text is available on this screen to assist you in determining which authorities you
should grant a user.
Tire System Access
Enter the Tire System Control File Maintenance from the File Maintenance Menu found
on the Tire System starting menu. The standard options for displaying, deleting and
editing are available, as well as the Add function.
The screen below illustrates the first page of the Tire System ACCESS record
maintenance for user Donna.
Notice Donna has been granted access to all functions shown on this screen. If an N
had been entered beside Purges, she would be unable to gain entry to any purge
options in the Tire System.
Accounts Payable Access
Enter the Accounts Payable Control File Maintenance from the Maintenance Menu found
on the Accounts Payable starting menu. The standard options for displaying, deleting
and editing are available, as well as the Add function.
The screen below illustrates the edit function maintenance screen for the Accounts
Payable ACCESS record for user Bud.
119
Notice that Bud has access to all Accounts Payable functions. If an N had been entered
beside Input, Bud would be unable to do any input in A/P.
General Ledger Access
Enter the General Ledger Control File Maintenance from the Maintenance Menu found on
the General Ledger starting menu. The standard options for displaying, deleting and
editing are available, as well as the Add function.
The screen below illustrates the edit function maintenance screen for the General
Ledger ACCESS record for user Bud.
120
Notice that user Bud does not have access to any G/L function, other than inquiries. He
would be able to inquire on a G/L account balance, but would be unable to do any other
task.
121
Daily Update
This option allows you to update your daily transactions to the master files. The scope
of the Update is determined by the values assigned to several Tire Dealer System
control keys and can include all the Tire Dealer System modules: Point of Sale, Order
Entry, Retread, General Ledger and Accounts Payable.
It is possible to update the system while active with the use of a control record. This is
not recommended. Saves and recoveries are the user's responsibility if updates are
performed on active systems.
Preparing to Run an Update
Authority to Run Daily Update
The user taking the option to run the Daily Update must have valid system access,
access for each software package (Tire, A/P, G/L) to update and store access to run the
update. Proper authority for the user profile is also required. Each access needed is
illustrated as follows.
Tire System Control File Maintenance Access
Above is the display of first screen for control record ACCESS in Tire System. Notice
access is allowed to both Update and EOM/EOY functions.
Access must be allowed for user profile running the update in Tire System, Accounts
Payable, and General Ledger control files.
Below, the user profile for the update must also have access to the stores that will be
updated.
122
User Profile Class and Authority
User profile for update must have correct User class… SYSOPR, and Special
authority.. *ALLOBJ, *JOBCTL, *SAVSYS, and *SPLCTL, to run the update and
save the data files.
Control Records for Update
When the update process begins, control key UPDATING is answered Y. This will keep
users from accessing the files, unless control key UPDTACTV is answered Y. This
allows the update process to run while users are actively working on the system. This
option is not recommended unless users must always be in operation, such as a 24 hour
a day business.
The UPDATING control key is maintained by the update procedure and should not be
changed by users unless an abnormal termination of the update occurred and you are
instructed to change this control key.
Update Screen Control Records
During an update, if control key UPDTPRCT is answered N, the Daily Update entry
screen is displayed. If UPDTPRCT is set to Y , the screen will not display at all and
the update will run according to control keys with no opportunity to change the values.
The following control records automatically answer the fields on the Daily Update
Screen, directing how the update will be run.
If control key JBQUPDT is set to Y , the "Run from JobQueue?" question on the entry
screen will be pre-answered with Y . This can be changed when performing a manual
update unless control key UPDTPRCT is answered Y.
123
If UPDTIPL is set to Y , the "Power down system?" question on the entry screen will
be pre-answered with Y . Note: If set to Y, an IPL cannot be run unless the update is
set to run from the job queue. This can be changed when performing a manual update
unless control key UPDTPRCT is answered Y. An IPL is routinely performed to ensure
users are off the system.
Control key UPDTTIME should contain the time you want the update to start. Enter
the time as military time but do not specify 240000, use 235959 instead. This can be
changed on the update front end screen when performing a manual update, unless
control key UPDTPRCT is answered Y.
Save Procedure Control Records
Control key USERSAV indicates whether you are using a custom save procedure in the
daily update procedure or the standard MaddenCo save procedure. USERSAV should
not be answered Y unless your company has a custom save procedure in your custom
library. If you answer this key Y and do not have a custom save procedure, you will not
get a save of your data files! Do not change the value of this key before consulting
Technical Support.
If USERSAV answered N, control key DISKSAVE is read to determine whether to save
your data files to a save file on disk during the daily update or save directly to tape. If
DISKSAVE is set to Y be certain control key SAVSAVFL is set to Y (if not – no save to
tape will ever take place.)
To save the data files to the correct save media/device, answer SAVMEDM with the
proper save media/device ID such as TC for tape cartridge.
If DISKSAVE is answered N and you are not using a customized save, you files will be
saved directly to the save media specified in control key SAVMEDM. If you are using
tape cartridges, control key SAVTAPDN contains the tape density to be used to
initialize your tapes.
The update initializes the tape for the data file save.
Printer Control Records for Update
UPDT and UPDTBAL for update reports and balance reports contains the default printer
control information for update reports. A PRINTER ID MUST BE ENTERED. This control
key can be assigned by store if you have more than one store and desire to print update
reports to a different printer for each store. IF A STORE MUST PRINT COMPRESSED,
USE 15 CHARACTERS PER INCH NOT 17. If only one control key is necessary, it should
not be assigned by workstation. The information kept in this printer control record is
form name or number, lines per page, characters per inch, lines per inch, last line to
print, start printing on line, printer id, number of copies to print, max characters per
line, and save after printing. Use the data code PR for formatted entry.
124
Auto Report Control Records for Update
To use the auto reports feature, answer control key AUTORPYN with Y and set up auto
report files thru Auto Report Maintenance. (See the Help Inquiry for more details.)
Auto Report files named BUP and BUP1 - BUP7 (1=Mon through 7= Sun) will run
before the update. Auto Report files named AUP and AUP1 - AUP7 will run after the
update. An Auto Report file called EOM runs at end of month, if control key EOMAUTO
is set to Y. Any report can be set up in the Auto Report program to run.
Reprint Update Reports
If control key UPRPTSAV is answered Y, update reports are saved after printing and
are moved to the QEZDEBUG out queue and can be reprinted any time within the next
seven days. After seven days, that set of update reports is automatically deleted.
Tire Dealer System Status Display of Control Records
You can take Option 17 on the Tire System Update Menu to display the update control
keys. These control keys will affect how the update is run. These control keys should
not be changed unless you are directed to do so. Please refer to the section on Tire
Dealer System Status for details on this feature.
Running a Manual Update
The Daily Update is located on the Update and EOM menu as shown below.
After completing authority and control record checks, you are ready to run a Manual
Daily Update. Take Option 1 on Update and EOM menu in Tire System.
The next screen will display giving the choice of running the update from the job queue,
powering down (IPLing), and the time to run the update.
125
As mentioned earlier in the Control Records for Update section, this screen is displayed
only if control key UPDTPRCT is set to N. The screen displays default answers to the
update questions based on control records JBQUPDT, UPDTIPL, and UPDTTIME.
These screen values can be changed to the currently desired settings.
After entering information on the update screen, the pop up window below displays the
answers chosen.
126
Automatic Daily Update on Job Scheduler
The job scheduler is a program created by IBM which allows AS/400 users to
automatically run jobs at predetermined times and dates, without having to be around
to start them in person.
The Daily Update can be set up in the Job Scheduler to be executed automatically at a
certain time each day for any particular day or days. When the update is done through
the job scheduler, work panels that prompt for input are not presented
If the update is set to run from the Job Scheduler, you will no longer take the option to
run the update from the menu each day. The update will run at the scheduled time
each day it is set to run or can be submitted to run immediately or at a specified time.
All that is required is remembering to put in the tape for the update file save. We can
even use the job scheduler to send a message to a user at a set time to give a reminder
to put the tape in.
The command to run the update is CALL PGM(GPTIRLIB/PTUPALL0). Note: this job
name ends in the number zero not the letter O.
Running a Job Scheduled Update
Please read ALL of the recommendations below. If these tips are not completely
understood, call Technical Support at MaddenCo BEFORE attempting them on your own.
1) The job scheduler cannot run a job that requires a front-end screen or has a pause or
informational message that must be answered. This means control key SYSDATE which
asks for the update date must be answered Y. This causes the system date to be used
as the update date. Control record UPDTPRCT must be set to Y so the update screen
does not display. The update will error if those keys are not set as they should be.
2) The user-id used to set the update on the job scheduler must have proper
authorities. Please refer to Authority to Run Update section covered previously in this
update document.
3) Control record UPDTTIME should be set to 000000, records SYSDATE, TIMERYN,
JBQUPDT, UPDTIPL, UPDTPRCT must be set to Y to run update from Job Scheduler.
These control records are explained in the above section on Control Records for Update.
4) Do NOT change the system date and/or time on the AS/400 without correcting the
job schedule entries. The submit date and time will be wrong after a date or time
change.
5) Change the update tape before the next update is ran. The update will initialize and
save the data files to tape. If the tape was not changed from the night before, the prior
day’s update save will be written over and thereby lost.
127
6) The easiest and safest way to run the update other than the normal scheduled time
is to take Option 10 to submit the Update immediately from the Job Scheduler or from
the Operations Window. If the update is to be run immediately instead of the regular
submit date and time, put the Update on hold – Option 3 on the Job Scheduler BEFORE
taking Option 10 to submit the update immediately. DO NOT FORGET TO RELEASE
THE UPDATE (Option 6) BEFORE THE SCHEDULED TIME ON THE NEXT DAY THE
UPDATE IS TO RUN.
Work with Job Scheduled Entries to Hold Update
Use Option 3 to hold the Update until you release it with Option 6 to run at the next
normally scheduled time.
128
Work with Job Scheduled Entries to Submit Update Immediately
7) If you are the only one signed on the system and an IPL is not necessary, the IPL
can be prevented. End PTUPWAIT from the active user screen (WRKACTJOB to locate
this program under the QBATCH subsystem) or use the Operations Window. Enter 4
beside the PTUPWAIT job and press F4, then set the How to end parameter to
*immed. This will end the IPL job before it gets a chance to run. The update
(PTUPALL0) will then begin to run WITHOUT IPLing. This must be done quickly;
however. Once the ‘system is going to power down’ message is displayed, there are
only minutes to cancel this update step.
Verify Save
You should verify that the save during the update was successful.
If you save to disk (control record DISKSAVE is set to Y), confirm a current save exists
by typing DSPSAVF FILE(SAVELIBR/QS36F).
129
In this example, the object TMCUST in the save file QS36F was saved on 9/7/00. The
complete update save information for your data files would contain many file names.
To verify information is being saved to tape, type DSPTAP DEV(TC) DATA(*SAVRST)
OUTPUT(*). This generates a report showing the saved files and the date they were
saved.
Update Reports
Update reports should be reviewed daily. Keeping up with the reports and error logs
that print assist in the accuracy of your system. Any postings that should be corrected
are best done daily instead of waiting until a problem has accumulated.
130
Standard update reports
Report
Name
PTPSHRBL
PTPSTBAL
PTCSHDW1
RTPRCCIN
RTPRCHIN
RTPRCVIN
PTPSHRBL
RTITRCPU
RTITIRGR
PTITGLUP
TNABUP1
PINVUPD
TARUP
TARUPBAL
PTUPALL1
TUPSLS
GUPAR
GUPJE
GUPAP
SYERRP
REPORT DESCRIPTION
First Invoice Rebuild Error Listing by Store
Out-Of-Balance Cash Drawer Worksheet by
Store
Total Cash Drawer Worksheet by Store
POS Recap of Closed Invoices by Store
Recap on Hold by Store
Recap Voided by Store
Second Invoice Rebuild Error Listing by Store
Receiving Update Register by Store and GL
Receiving Postings
Invoice Audit List by Store
Invoice Register by Store
Invoice Update GL Posting Report by Store
National Account Billing Credit Memo Register
Vendor Invoice Input Register
Accounts Receivable Register by Store
Accounts Receivable Balance Register
Total Sales Balance Information Register
Accounts Receivable Update to GL
Journal Entry Update to GL
Accounts Payable Update to GL
Error Log List
Finding Update Reports
Update reports are set to print automatically after the update is run. If the reports jam
on the printer or for any reason you wish to reprint the reports, the following
information will assist you.
To view the update reports on the update out queue before they print, use the
command WRKSPLF SELECT(UPDATE) if the user profile is Update for the daily
update or chose the option for Update Reports on your Operations Window.
131
Update Reports O% Control Record in Operations Window
Updates running from the job scheduler are usually set under the Update user id. To
see these reports, add a O%99 (where 99 is number up to 30) control record for the
Update user profile with the description Update Reports, C for command, WRKSPLF for
program, and for command parms type SELECT(UPDATE).
Reprint up to 6 Prior Days of Update Reports
To view or reprint up to 6 prior days of update reports, use the command WRKOUTQ
QEZDEBUG or use the following for an Operations Window option.
Add an O%99 (where 99 is number up to 30) for your user profile with the description
‘6 Days of Update Reports’, C for command, WRKOUTQ for program, and for command
parms type OUTQ(*LIBL/QEZJOBLOG).
132
Balancing Update Reports
Several reports print at the end of the update to help you confirm data is posting
properly.
Balancing Accounts Receivable
Begin by locating the Accounts Receivable Balance Register from the previous update.
Find the Current A/R balance amount.
Accounts Receivable Balance Register, previous update
In this example, the amount is $3,418,182.85. This amount should be copied to the
Total A/R from prior update field on the Accounts Receivable Balance Register for
the update being balanced. Add this amount to the net change in A/R amount on the
register.
3418182.85
3420258.28
BALANCED
133
For our example, add $3,418,182.85 and $2,075.43 to yield $3,420,250.28.
amount equals the printed Current A/R balance, so our update is in balance.
This
Discrepancies can occur when postings are incorrect (perhaps a type of sale is not
properly flagged). If you have generated or written off service charges, these functions
affect A/R outside of a normal update. The amounts reflected by these steps must be
added into the Total A/R from prior update amount to be properly accounted for.
Balancing Sales
Begin by locating the Sales Update BALANCING TOTAL SALES INFORMATION page from
the previous update.
Total Sales Information Register, previous update.
Find the Current Sales amount. In our example, this figure was $11,850,113.87.
Copy this amount to the Previous Current Sales field on the current update’s
BALANCING TOTAL SALES INFORMATION report. Add these amounts together to yield
the total.
134
Balance Total Sales Information Register
11850113.87
11852391.79
Balanced
In our example, Previous current sales of $11.850,113.87 Plus Sales added of
$2,277.92 Equals $11,852,390.07. This amount matches the Current Sales amount,
so our sales figures balance.
Update Error List
Occasionally, problems with update postings occur. Perhaps a necessary G/L posting
control key is not on file or a product was not found for inter-company receiving.
The update calls your attention to problems with the Error Log List. This report prints at
the end of the update reports and indicates problems that need to be resolved.
See the Error Log section of this manual for more detailed information on resolving
these issues.
135
System Operator’s Log
Purpose of System Operator’s Log
The System Operators log is used to record daily system information, questions,
operations, or problems. A simple spiral notebook works well. Entries should be clearly
dated so they can easily be located. Retain the logbooks for perhaps a year in case
there might be questions on previous activities (such as what procedures were followed
for last end of year).
What to Write in a Log Book
Record operations performed during the day. If a purge is performed, log which purge,
pertinent dates and perhaps how long the purge took.
Record questions and answers about system operations. Who asked about what , the
information you gatherer and the ultimate answer. If you worked with someone at
MaddenCo, record who it was. If you have the support tracking number, enter it.
System messages and solutions can be logged. Again, it is very important to put these
notes in the Operator Manual to locate them again easily.
Program error messages and their corrections should be logged.
Clip print keys and other papers to that day’s page to find them quickly or use any way
that will help to keep your documents together.
136
Security
Overview
The AS/400 has five levels of security available. These are numbered 10 thru 50, with
increased security as the levels increase: level 10 has no security at all, level 50 is so
secure you may not be able to use the system yourself.
We ship the system at security level 20, which is PASSWORD ONLY. We believe this
level, along with the following suggestions; provide sufficient security for most of our
clients. If, after implementing these suggestions, you think you still need a more
secure system, we can recommend a good book that discusses level 30 security. The
authors of this book might be able to advise you on level 50, if you believe you need
more security.
All levels of security (except level 10) use a password to grant access to the system. If
passwords are common knowledge, you might as well set your security level back to
level 10. Later we will discuss ways to help keep passwords secret.
Central to setting up a secure system are passwords and authorities stored in user’s
profiles, system values, assigned menus and access control records for every Tire
Dealer System module. We feel these features will make your system reasonably
secure.
User Profiles
In an earlier section of this manual, we discussed creating user profiles (or user ids).
Below are some suggestions for additional user profile changes to secure your system.
137
To access a particular user profile, enter CHGUSRPRF user id and press F4. Enter the
user id you wish to change and press enter.
Notice that our user Bud will be signing onto a custom menu by way of the Initial
program to call parameter value of PSTARTUP. Also notice that Bud’s Initial Menu
has been set to *Signoff. If he attempts to leave his assigned menu, he will be signed
off the system.
We can further restrict Bud’s ability to access other menus by changing some additional
parameters.
Limit capabilities secure a user to a particular menu when signing on. Setting this
parameter to *YES will allow the user to only run options from the menu he is assigned
to. The limit capabilities parameter has the following possible values: *NO,
*PARTIAL and *YES. See the following table for how this affects the user:
*NO
User
User
User
User
User
138
can
can
can
can
can
change initial menu at sign on
change initial program at sign on
change current library at sign on
change attention program
enter OS400 commands on
command line
yes
yes
yes
yes
yes
*PARTIAL
*YES
yes
no
no
no
no
no
no
no
yes
no
You can also limit the number of screens a user can be signed onto. Press F10 for
additional parameters and roll the screen.
Change Limit device sessions to *yes to restrict the user to a single session.
System Values
IBM system values control different aspects of the operating system. They are accessed
with the WRKSYSVAL command.
Some of the system values affecting security are:
QDSPSIGNINF shows additional information at sign on. When this value is set to 1,
information is displayed about the date and time this user was last signed on and the
number of invalid sign on attempts since the last sign on. This is a good way to see if
someone is fishing for passwords.
QMAXSGNACN tells the system what to do if someone is continuously attempting to
sign on to your system with an invalid User id or password. We recommend you set this
to 3 to disable the device they are trying to use and to disable the user profile.
QMAXSIGN is the number of failed sign on attempts allowed before the above disabling
takes place. Be sure to allow a sufficient number of attempts to allow for Monday
morning fumbling.
139
QLMTDEVSSN is the system wide default that determines if a user may be signed on to
more than one terminal at a time. A more restrictive value for a particular user can be
set on that user’s profile.
QPWDEXPIVT specifies how often users must change their passwords. This can also
be set in each user profile; however, we recommend this be set here. 30 to 90 days
seems a reasonable time frame.
QPWDRQDDIF requires a changed password to actually be a different word. Set this
value to (0 - the default.)
Custom Menus
When you sign onto the system, you are presented with a menu. From this menu you
can run programs, go to other menus and usually enter system commands. The menu
you see when you sign on is designated in your user profile. We typically set your
menu to the Tire Dealer Start menu. From this menu you can go to any menu in our
system; however, this might not be advisable for all the users on your system.
We include a feature called User Menus with the system. This system allows you to
create custom menus using a User Menus Maintenance function (located on the System
Menu.)
We recommend you create a custom menu for each function in your company. For
example, a different menu could be created for store salesmen, store managers, a
credit manager and even one for your company’s president. Just put inquiries and
reports on the president’s menu (you don’t want a president to input anything – it would
probably be wrong.)
From within the User Menus Maintenance, you can assign each person to a particular
menu. At sign on, the user’s profile will point to this customized Menu System entry to
locate the proper menu to display.
Details on setting up custom menus can be found in the User Menu manual.
Access control records
The System Menu contains a security feature called Store Access. Each user id must
be specifically granted access to individual Tire Dealer System modules at each store in
order to use that portion of the programs at a particular location.
Additionally, each Tire Dealer System module adds it’s own level of security thru the use
of ACCESS keys. These keys are set up for individual user ids and contain entries for
various functions that can be permitted or denied. Further restrictions can be added
with the ACCESEXP key. If this Tire System control record is answered with a Y,
individual features must be explicitly allowed on a valid ACCESS key or no processing is
allowed for that particular user.
See the earlier section on ACCESS for more details.
140
Operations Window
Users in any Tire Dealer System module can access a pop up menu allowing them to
perform simple system functions like reviewing print queues and checking for messages.
See the Operations Window section for ways to limit the options offered to specific users
on this window.
When Someone Leaves the Company
When an employee leaves the company, you should curtail their access to the system
immediately. Your first thought may be to delete their user profile altogether, which will
certainly eliminate their use of the system. However, through their day-to-day use of
the system their user id has probably created objects (files or spooled reports), which
they now ‘own’. You cannot easily delete a user profile if it owns objects. So, instead of
deleting the user profile, merely set it to disabled. Use the Status parameter in user
profile maintenance (WRKUSRPRF) to change the user’s status to *disabled. See the
section on User Profiles for more details on working with user profiles.
Allowing Access to the System for an Outside User
You may want to allow certain people to have very limited access to your system.
These limited users may not even work for your company. For example, we have a
program that allows your customers to input their own orders into our Order Entry
System. (See the Order Entry Module help section on Limited Order Entry for more on
setting this up.)
By using the Initial program to call and the Initial menu parameters on a user’s
profile, you could create a profile for one of these customers that would execute the
Limited Order Entry program as soon as they sign on, then sign them off when they end
this program. These users would have no other access to your system.
See the section on User Profiles for help creating a new user profile.
For our example we would set:
Initial program to call ……………………………….PTPSLOEW
Initial menu …………………………………………………*SIGNOFF
Limit capabilities………………………………………….*yes
141
At this point, we need to press F10, and roll the screen twice to set Attention
program to *None
Remember to grant this new user Access and authority to execute this program.
See the section on Access for more details.
Final Suggestions
Securing your system is mostly common sense, but here are some reminders, anyway.
142
All system supplied profiles should have their passwords changed as soon as possible.
When the system is shipped, the passwords are set to the user profile name for
QSECOFR, QSYSOPR, QUSER, QSRV and QPGMR. Everyone in the business
(computer business, that is) knows these passwords, so change them. While you’re at
it, set these new passwords so they won’t expire (Set password to expire parameter
on the user profile screen.) Don’t forget to record the new passwords and store them in
a secure place.
Disable user profiles for employees that leave the company. Do it immediately or you
may forget. If someone with security administrator authority leaves, be sure to change
the passwords for the system supplied profiles (QSECOFR, QSYSOPR, etc.) Again,
store the new passwords in a secure place.
Do NOT use the QSECOFR profile as a regular sign on id.
Set up more than one user profile with *SECADM authority. If you are on vacation,
someone else may need this authority.
Do NOT leave your terminal signed on when you are away from your work area – EVER.
Do NOT disclose your password. Do not write it down on a sticky note stuck to your
terminal. Do not use your workstation record and play keys for signing on.
Set passwords to expire. This will remind users to keep the system secure. Typically,
when you start up a system, passwords are ‘fun’ to tell each other. This will fade and
by forcing a change, the passwords will no longer be common knowledge.
143
144