Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
System Information form an AS400
- Thread starter Krash878
- Start date
What do you mean by "system information"?
If you are using WRKSYSVAL, you can get all of those values in a CL program by using the RTVSYSVAL command (or in another HLL program by using the QWCRSVAL API).
"When once you have tasted flight, you will forever walk the Earth with your eyes turned skyward, for here you have been, and there you will always long to return."
--Leonardo da Vinci
If you are using WRKSYSVAL, you can get all of those values in a CL program by using the RTVSYSVAL command (or in another HLL program by using the QWCRSVAL API).
"When once you have tasted flight, you will forever walk the Earth with your eyes turned skyward, for here you have been, and there you will always long to return."
--Leonardo da Vinci
- Thread starter
- #3
I need to log all the information on multiple AS/400s that appears on screen with the following commands.
DSPPTF
DSPHDWSRC
DSPSYSVAL QSRLNBR
DSPSYSSTS
WRKLICINF
DSPDEVD
There is a portion of each screen that I need to maintain a Database on. We want to have the everything from the processor to the tape drives. We also need to know how much of the storage capacity is currently being used. I deal with just over 50 AS/400's and this can get very time consuming.
Thanks
Krash
DSPPTF
DSPHDWSRC
DSPSYSVAL QSRLNBR
DSPSYSSTS
WRKLICINF
DSPDEVD
There is a portion of each screen that I need to maintain a Database on. We want to have the everything from the processor to the tape drives. We also need to know how much of the storage capacity is currently being used. I deal with just over 50 AS/400's and this can get very time consuming.
Thanks
Krash
A lot of these commands can produce spool files and/or output files, which you can FTP back to the "home" system for processing. The outfiles should all have a field for the system name, so you can differentiate systems.
For the commands that only output spool files, you'll need to copy the spool file to a physical file with a record length of 133 and use a HLL program to process it (I have also done that with good old Query/400, by defining the headers on the reports and excluding them, and sending the result to an outfile).
There may be API's to do what you want (I know about QWCRSVAL, which is the equivalent of RTVSYSVAL), you might want to see if you can use these API's in a CL or RPG program on the remote systems to get your data. Then, it's just a matter of getting all the info over to the "master" database.
It will be time consuming, also, to write this application, but it should be worth the effort. Good luck.
"When once you have tasted flight, you will forever walk the Earth with your eyes turned skyward, for here you have been, and there you will always long to return."
--Leonardo da Vinci
For the commands that only output spool files, you'll need to copy the spool file to a physical file with a record length of 133 and use a HLL program to process it (I have also done that with good old Query/400, by defining the headers on the reports and excluding them, and sending the result to an outfile).
There may be API's to do what you want (I know about QWCRSVAL, which is the equivalent of RTVSYSVAL), you might want to see if you can use these API's in a CL or RPG program on the remote systems to get your data. Then, it's just a matter of getting all the info over to the "master" database.
It will be time consuming, also, to write this application, but it should be worth the effort. Good luck.
"When once you have tasted flight, you will forever walk the Earth with your eyes turned skyward, for here you have been, and there you will always long to return."
--Leonardo da Vinci
- Status
Similar threads
- Locked
- Question