× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


lately I changed my backup strategy to have included QDLS, and IFS into my incremental dailies. (I recently have learned that there is a CHGPERIOD(*LASTSAVE) parameter to be used with SAVDLO, and SAV.) I'm using V4R5 on my venerable 150, if this is relevant.

On April 10 I added a file (a picture) into my web tree in /QOpenSys, and also changed the referring html page.

The next day, both weren't listed in the spool file resulting from OUTPUT(*PRINT). I wonder why that is. I expect new and/or changed files to be included with the save.

Both files have a "changed" timestamp of both file attributes, and file data resulting from the upload on April 10. The last Save 21 was on April 3. I could not see any "last saved" shown on the attributes when navigating with WRKLNK, using option 8

I'm using the save command as follows:


Any ideas about this — to me — unexpected behavior?

Note: &EXPDATE is a date I'm calculating in the CL code before to make the content expire after 27 days.

Note 2: I encountered that I needed to use ('/QDLS' *OMIT) instead of ('/QDLS/*' *OMIT). I thought it to be a good idea to keep the empty folder intact in IFS so the file system could be mounted after a restore. Sav wasn't happy about that and rejected the entire command line. :-) Same goes for /QFileSvr.400, /QNTC, and /QSYS.LIB.

:wq! PoC

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2023 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.