System Operator s Guide. MaddenCo Inc. Revised August Copyright 2003 by MaddenCo, Inc All rights reserved.

Transcription

1 System Operator s Guide MaddenCo Inc. Revised August 2003 Copyright 2003 by MaddenCo, Inc All rights reserved. 1

2 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

3 Table of Contents AS 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 Commonly Used Commands Cleanup Output Queues Creating an Archive Output Queue Using the Clean Output Queues Function CLNUPOUTQ Examples Delete all spool files more than 60 days old Delete everything from the Archive that is over a year old Additional Information Printer Commands: WRKWTR Work with printers WRKOUTQ Locate reports for specific printers WRKSPLF Locate reports for specific users Changing print spool entries: Viewing a Report without printing: Deleting spool files that you no longer need: Other options available for spool files: Other Function keys available for spool files: Tape Drive Commands: INZTAP Initializing a Tape SAVOBJ Save Objects to Tape SAVLIB Save a Library to Tape SAVSAVFDTA Save a Save File to Tape DSPTAP Display the contents of a Tape RSTOBJ Restore Objects from a Tape RSTLIB Restore a Library from Tape System Commands and Functions : WRKSYSVAL Work with System Values Changing the system date Changing the system time WRKSYSSTS Work with System Status Disaster Recovery System Save Performing a System Save Job Scheduler Reorganize OS400 Release Levels AS/400 Logging What is logging? Interactive Job Log Batch Job Log System History Log System Messages Displaying System Messages Automatically Answer Messages Batch Jobs Where do batch jobs go? When are batch jobs finished?

4 4 Where are the reports? Can t find a report? Other report handling features Hardware and Communication Guidelines AS/ Powering Down the System Power Down the System Without Restarting Power Down the System and IPL to Bring up the AS/ IPL the AS/400 After Powering Down Without Restart Manual IPL Moving your AS Battery Backup Troubleshooting Hardware Problems AS/400 Down Remote Store Down Terminal or Printers not Functioning Ethernet Communications Problems MaddenCo Tire Dealer System Help Inquiry Help Inquiry Sections Using Help Inquiry Printing Help Inquiry Online Help Is Available Turning on New Features Looking up Control keys Printer Control Keys MaddenCo Technical Support Getting ready to call Technical Support Faxing information to Technical Support Calling Technical Support Emergencies Connect/Connect How to Sign MaddenCo onto your AS/ Before Connecting Work with Line Configuration Status How to Connect Connection Messages Tire Dealer System Options and Features Running Multiple Batch Jobs using Multithreading Operations Window Setting Up the Operations Window Suggested Options for Operations Window Command List Program List Warning Inquiry Window Warning Customer Inquiries Product Inquiries Invoice History Inquiries Other Inquiries Purchase Order Input Accounts Payable System Inquiries Retread System Inquiries...106

5 G/L Matrix List Display Tire System Status Purges General Guidelines End of Month End of Year Access System ACCESS Copy a User s Control Records Store Access Maintenance Control File Maintenance System Access Control Maintenance Tire System Access Accounts Payable Access General Ledger Access Daily Update Preparing to Run an Update Authority to Run Daily Update Control Records for Update Save Procedure Control Records Printer Control Records for Update Auto Report Control Records for Update Reprint Update Reports Tire Dealer System Status Display of Control Records Running a Manual Update Automatic Daily Update on Job Scheduler Running a Job Scheduled Update Work with Job Scheduled Entries to Hold Update Work with Job Scheduled Entries to Submit Update Immediately Verify Save Update Reports Standard update reports Finding Update Reports Update Reports O% Control Record in Operations Window Reprint up to 6 Prior Days of Update Reports Balancing Update Reports Balancing Accounts Receivable Balancing Sales Update Error List System Operator s Log Purpose of System Operator s Log What to Write in a Log Book Security Overview User Profiles System Values Custom Menus Access control records Operations Window When Someone Leaves the Company Allowing Access to the System for an Outside User Final Suggestions

6 6

7 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

8 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

9 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

10 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

11 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

12 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

13 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

14 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

15 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

16 Delete all spool files that are 60 days old except any spool file on PRT05. 16

17 Delete everything from the Archive that is over a year old 17

18 Archive reports ran by user DAVISJ that are more than 28 days old. 18

19 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

20 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

21 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

22 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

23 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

24 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

25 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

26 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

27 +5 move the screen down 5 lines -5 move the screen up 5 lines P10 - 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

28 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

29 Other Function keys available for spool files: From the WRKSPLF screen, there are several Function keys available: F3 - will return you to the screen where you originally initiated the WRKSPLF command F10 will display additional attributes about the report F11 will display additional attributes about the report F18 will take you to the bottom of all of your spool files F17 will take you to the top of all of your spool files F22 will take you to a screen where you can manage all printers. This is the same function as the WRKWTR command. 29

30 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

31 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

32 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

33 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

34 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

35 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

36 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. Store your save off-site in a safe place where it can be retrieved quickly should it be needed. 36

37 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

38 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

39 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

40 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

41 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

42 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

43 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

44 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

45 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

46 This is an example of the History Log Contents. 46

47 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

48 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

49 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

50 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

51 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

52 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

53 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

54 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

55 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

56 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

57 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

58 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