What’s In A Save File?
October 4, 2016 Ted Holt
Note: The code accompanying this article is available for download here. Juliet wondered, “What’s in a name?” Ted wondered, “What’s in a save file?” The Display Save File (DSPSAVF) command would show me only so much, so I wrote a utility to give me more information. Maybe it will be helpful to you. It’s common for me to exchange save files with other IBM i professionals. One problem I often run into is that someone (who might be me) cannot restore a save file to their system because the save file was created for a more recent release of IBM i. I needed a way to determine this information, and DSPSAVF did not have it. Fortunately, IBM’s QSRLSAVF API lists more information than what DSPSAVF shows. My utility is called Print Save File, and it consists of three objects:
It also requires Brian Rusch’s magnificent message-forwarding commands, MOVPGMMSG and RSNESCMSG, which were published in the May 2, 2012, issue of Four Hundred Guru. Here’s a sample of the report. Save file: *LIBL/BASSSAVSRC --- Input Parameter Section --- User space ............: PRTSAVF000 Library ............: QTEMP Format ................: SAVF0100 Save file .............: BASSSAVSRC Library ............: *LIBL Name filter ...........: *ALL Type filter ...........: *ALL Continuation ..........: 404040404040404040404040404040404040404040404040404040404040 --- Header Section --- User space ............: PRTSAVF000 Library ............: QTEMP Save file .............: BASSSAVSRC Library ............: THOLT Continuation ..........: 404040404040404040404040404040404040404040404040404040404040 --- General Information (SAVF0100) --- Library ...............: BASSSRC Command ...............: SAVOBJ Save date/time ........: 2016-06-01 08:13:39 ASP ...................: 1 Records ...............: 1968 Objects ...............: 1 Access paths ..........: 0 Save while active .....: *NO Release ...............: V7R1M0 Compressed ............: 0 Serial number .........: BR-549 Private authority .....: 0 ASP name ..............: *SYSBAS Members ...............: 26 Spooled files .........: 0 Sync ID ...............: *NONE --- Objects (SAVF0200) --- --- 1 --- Object ................: BASSSRC Library ...............: BASSSRC Type ..................: *FILE Attribute .............: PF Save date/time ........: 2016-06-01 08:13:39 Size ..................: 1216512 Multiplier ............: 1 ASP ...................: 1 Data saved.............: 1 Owner .................: QPGMR DLO name ..............: Folder ................: Text ..................: BASS source code ASP name ..............: *SYSBAS --- Members (SAVF0300) --- --- 1 --- File ..................: BASSSRC Library ...............: BASSSRC Member ................: PSDS Attribute .............: PF Save date/time ........: 2016-06-01 08:13:39 Members ...............: 26 --- 2 --- File ..................: BASSSRC Library ...............: BASSSRC Member ................: PASS1PROTO Attribute .............: PF Save date/time ........: 2016-06-01 08:13:39 Members ...............: 26 --- 3 --- File ..................: BASSSRC Library ...............: BASSSRC Member ................: PASS2PROTO Attribute .............: PF Save date/time ........: 2016-06-01 08:13:39 Members ...............: 26 /////////////////////////// --- 26 --- File ..................: BASSSRC Library ...............: BASSSRC Member ................: BASSPASS2 Attribute .............: PF Save date/time ........: 2016-06-01 08:13:39 Members ...............: 26 --- Spooled files (SAVF0400) --- ** End of report ** Status=00 The report begins with general information about the save file. This is followed by objects, file members, and spooled files. Here are a few things to be aware of.
Feel free to improve it. Ted Holt welcomes your comments and questions. Email him through the IT Jungle Contacts page. RELATED STORY
|