Using the Electronic Service agent, your iSeries system can automatically order fixes and report pending or actual hardware or software problems to IBM. Prior to V5R3 of OS/400, this function was packaged as a separately installable licensed program, 5798RZG. Now, the function has been repackaged into the base operating system, making it even easier to work with.
How to set up the Electronic Service agent
Just prior to doing your V5R3 upgrade, after you do your pre-upgrade full system save, you should run DLTLICPGM against the old version of Service Agent. The command is DLTLICPGM LICPGM(5798RZG). Since the new version of the program uses the same library, it is good to delete the old version so that you can be assured that the library was replaced. DO NOT wait until after you upgrade to run the DLTLICPGM because that will remove critical pieces of the new Electronic Service Agent function.
More Information
[IMAGE]
You should also write down the communications resource for the QESLINE, which can be found with the command DSPLIND QESLINE. You will need this resource name later on when you configure the new version of Service Agent. Last, you will need to know whether you have an internal or external modem and its model number. (See Figures 2 and 3 for the list of modems that configuration presents to you.)
Once you have completed your V5R3 upgrade, you should install the ...
To continue reading for free, register below or login
To read more you must become a member of Search400.com
');
// -->

group PTF for Electronic Service Agent, SF99298 to ensure you have all the latest fixes. Then you can run the command GO SERVICE from a command line. You will be asked to configure either an *ECS or *SRVAGT connection. It is best to start with the *ECS configuration, as this is a little easier to get working. Once the *ECS connection is working and verified, you can run through the process a second time to create the *SRVAGT configuration.
You will see a screen similar to the one shown in Figure 1.
Figure 1: The CRTSRVCFG screen
The value you use in the Connection type parameter will most likely be *PTP (for point to point), unless you plan to connect through a virtual private network.
Specify *ECS for the Service parameter and *SELECT for the other parameters, as shown in Figure 1. There are some additional parameters on a second screen, but you should not need to change them from the defaults.
By specifying *SELECT for the parameters as shown in the example, you will be presented with several screens where you can select the option that is appropriate for your installation. Here are some tips to help you with selections:
If you are in the U.S., then you may want to select *NATIONWIDE (at the bottom of the list of choices) for State or Province number . You will then be given a couple of toll-free numbers to select from for Primary and Alternate telephone numbers. When entering the phone numbers, make sure you append a '9' if you need to dial for an outside line. You also need to make sure there is a '1' in the telephone number, as in 1-800-xxx-xxxx. IBM has shipped some phone number files without the '1' appended. Note: In the telephone number, you can use a comma (,) wherever you want the dialing sequence to pause for a second.
Enter the correct modem information from the list, using the information you gathered previously. The list of modems looks like that shown in Figures 2 and 3. If your modem does not match any of these selections, it is probably best to contact IBM rather than trying to guess.
Figure 2: List of modems, page 1
Figure 3: List of modems, page 2
You can then hit Enter, and your configuration should be created. If you experience problems, a call to IBM support is probably in order, as there are a lot of things that can go wrong.
There is a verify function from the GO SERVICE menu (option 17) that you can use to test your configuration. The first time you connect to IBM it may run especially slow, so be patient. Also, we have noticed that in general the connection process for commands such as SNDPTFORD run more slowly than they did in previous releases.
-----------------------------------
About the author: Dan Reusche is a senior systems administrator at Think Federal Credit Union in Rochester, Minn. He has worked with the IBM AS/400 and iSeries platform since 1988, when he worked at the IBM Rochester Development Lab and support of AS/400 systems used within IBM. You may contact him at dreusche@chartermi.net.