Depending on your release and language code the file name will differ.
In Guy's note, Q5763SS1320240003 breaks down as follows:
Q - just cuz it's IBM
5763SS1 - your OS/400 Licensed program (for V2 5738SS1, for V3 RISC 5716SS1)
320 - Version, Release, Modification level
24 - Last 2 digits of you language code (ie. 2924 - English Upper/LowerCase)
0003 - designates 3rd file for language objects from SAVSYS command.


On Tue, 14 Oct 1997, Guy Murphy wrote:

> 
>         Mr. Barsa is indeed correct.  When I do a SAVSYS, I use the *PRINT 
>      output option.  Nothing in that report looks like a QHST* file.  
>      However a DSPTAP with a *SAVRST shows the QHST* files.
>         Below is a copy of my output from the SAVSYS command.  The QHST* 
>      files are in Q5763SS1320240003, file sequence 9.  Not exactly obvious 
>      but that's not an excuse for not looking deeper into the matter.
>      
> 5763SS1 V3R2M0  960517  Save System - Label Information         
> 
> Device . . . . . . . . :   TAP02                                              
>  
>                    
> Data compressed  . . . :   Yes              Data compacted . . . . :   Yes    
>  
>                    
> Expiration date  . . . :   *PERM                                              
>  
>                    
> File                                    File                                  
>  
> Label              Library   Volume     Sequence  Text                        
>  
> 
> QFILEIML                     WS2200        1      Licensed Internal Code file
> QFILEMCD                     WS2200        2      Licensed Internal Code file
> QV3R2M0.L2924      QSYS      WS2200        3      Language feature code file
> QFILEIPL           QSYS      WS2200        4      Initialization file
> QFILEIN            QSYS      WS2200        5      Initialization file
> Q5763SS1320M.0001  QSYS      WS2200        6      Program objects library QSYS
> Q5763SS1320240001  QSYS      WS2200        7      Language objects library 
>QSYS
> Q5763SS1320240002  QSYS      WS2200        8      Language objects library 
>QSYS
> Q5763SS1320240003  QSYS      WS2200        9      Language objects library 
>QSYS
> Q5763SS1320M.0002  QSYS      WS2200        10     Program objects library QSYS
> QFILEUPR           QSYS      WS2200        11     Security data
> QFILEIOC           QSYS      WS2200        12     Device configuration objects
> 
>                          * * * * *   E N D   O F   L I S T I N G   * * * * *  
>  
>               
> 
> 
> 
> At 09:38 AM 10/13/97 -0600, you wrote: 
> >
> >        I don't believe that the QHST* files are saved by the SAVSYS 
> >     command or by any other SAV* command unless it's done explicitly by 
> >     name.  What we do is move any QHST* files older that 2 weeks to a LOG 
> >     library we create and save the lib (it takes QSECOFR authority to move 
> >     the QHST* files).
> 
> With all due respect, this is incorrect.  QHST* files are saved as a part of 
>a 
> SAVSYS.
> 
> Al
> 
> 
> 
> Al Barsa, Jr. - Account for Midrange-L Barsa Consulting, LLC.        
> 400 > 390
> 
> 
> 
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
> | To unsubscribe from this list send email to MAJORDOMO@midrange.com
> |    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].