I have the evaluation version of the iSeries Report Downloader. How do I extend the Downloader’s evaluation period?
When an expired copy of the evaluation version of the Downloader is launched, it will allow you to enter a key code to extend the evaluation period another 20 days.
This key code is: 0821
Key this number in and click "OK" (be sure to include the leading zero.) You will have to key in this value each time an expired Downloader evaluation is started.
After an additional 20 days the Downloader evaluation will expire and can't be extended.
How is the user's access to spool files controlled?
Evergreen Interactive’s iSeries Report Downloader uses ordinary iSeries output queue security to control user access. That is, if a user can access an outq or a spool file’s contents from a 5250 display command line, then he/she can access them through the Downloader. Similarly, if a user can’t see the outq or spool file contents from a 5250 command line then he/she won’t be able to access them from the Downloader. Access to an outq is controlled by two means within iSeries security access to the outq itself and access to individual spool files within an accessible outq. You control access to the outq by setting its *PUBLIC authority to *EXCLUDE with the Revoke Object Authority CL command: RVKOBJAUT OBJ(QGPL/PAYROLL) OBJTYPE(*OUTQ) USER(*PUBLIC) AUT(*ALL) Control access to individual spool files’ content within an outq with the Change Output Queue CL command. For example: CHGOUTQ OUTQ(QGPL/PAYROLL) DSPDTA(*OWNER) This specification will only allow a spool file’s owner to access its content. Then, only those users with explicit authority to the outq may display the spool file entries it contains. Users with *JOBCTL authority can see the spool file entries in the outq but they may not see the contents. The owner of the spool file and those with *SPLCTL authority may manage the spool file as well as access its content. You can test out these features from a 5250 command line – it will work the same with the Downloader.
Why does the Downloader create a user profile?
Each user of the Report Downloader runs under his/her own user profile, rather than under the user profile of the person who started the main Downloader server program. This is required so that user's access to iSeries objects comes under your ordinary security control. In order to accomplish this, the main server program (job DLOADERSRV in subsystem QSYSWRK) must have sufficient authority to check the user ID and password of each user that requests services. The user ID and password are checked through means of an IBM API and, if valid, a spawned server job is started under the user's own profile. Also, under this API, unsuccessful signon attempts made through the Downloader are accumulated in the user's profile just like during green-screen signon attempts and may likewise result in a disabled profile. The Downloader's installation process creates a security officer level profile named DLOADER. The DLOADER user profile is created by the Downloader installation with a password of *NONE and can not be used to sign on to your iSeries. Note: Any user can start the Downloader's main server job with command VBTCP/STRDLOAD, and the server will still run under the DLOADER profile.
How do I start the main server program on the iSeries?
The main server program may be started from an iSeries command entry line or from a CL program (like QSTRUP in QGPL.) In either case, use iSeries CL command: VBTCP/STRDLOAD to start the main server program. Alternatively, if your iSeries has FTP active, a user may issue the STRDLOAD command remotely from the PCs Downloader program (the user is prompted for a userid and password even if a password has been saved.) You need no special authority to start the main server program.
What if there's a firewall on my iSeries? What TCP/IP ports does the Downloader use?
A "firewall" is security software that blocks unauthorized access to your iSeries. In order to run the iSeries Report Downloader you must open certain TCP/IP ports (note that the Report Downloader uses full iSeries system security to control access.): Port 17850 is used by the main server program. This port must be opened. Ports 17851 through 17950. When a user starts the Report Downloader the main server program will look for an available port between 17851 and 17950. You must at least open port 17851. If you expect multiple concurrent users you should open more ports beginning with port 17852 through the number of concurrent users you expect. All TCP/IP client/server applications run through ports on your iSeries. Telnet runs through port 23, smtp run through port 25, pop3 runs through port 110, etc. In TCP/IP client/server applications, the active server program, listening on the port, is responsible for security. The iSeries Report Downloader uses regular iSeries system security to prevent unauthorized access. You can view the ports that are being used by active TCP/IP servers by keying NETSTAT *CNN at an iSeries command line. Press F14 to see port numbers used.
How do I get the Downloader server program to start automatically?
You may decide that you want the Downloader’s main server program to always be active, and you would like it to start automatically without any operator action. You may do so by including the command VBTCP/STRDLOAD in CL program QSTRUP in library QGPL. The QSTRUP program is always called by OS/400 at the end of an IPL (indeed, this is how your various subsystems get started.) The source code for QSTRUP is located in QCLSRC in library QGPL on most iSeries. If you do not find the source code for QSTRUP, you may retrieve the program's source code with CL command RTVCLSRC (retrieve CL source). PLEASE NOTE: All iSeries system level TCP/IP support must be completely initialized and started before the Downloader's main server program may be started. If you're going to use the QSTRUP program to start the Downloader, you should place a DLYJOB DLY(1200) (delay job for 20 minutes) CL command in your QSTRUP source code. Place the DLYJOB command after the statements to start subsystems and TCP/IP and before the command to start the Downloader main server program.
How do I check to see if the main server program is active?
You may check the status of the main server program with CL command:
You'll receive a message displaying the status of the main server program. You can also look directly into the subsystem QSYSWRK and look for the main server program (job named DLOADERSRV) as well as spawned server programs (jobs named DRPT17xxx.)
How do I use an Excel or Word macro to automatically process the downloaded report data?
The Downloader can invoke a macro to complete processing over the spool file data. You must create and store the macro statements ahead of time, usually in a template document or spreadsheet (like "Normal.dot" or "Personal.xls".) You can use Excel's or Word's macro recorder to generate your macro statements if you wish. Just load a spool file to Excel/Word, start the macro recorder and perform the steps that you would like to capture. Then turn the macro recorder off. The next time you process the same type of report you may invoke the macro by name directly from the Downloader.