Home > IT Answers > AS/400 > Omit on a SAV command
Rjrohwer
25 pts.
 Omit on a SAV command
AS/400, AS/400 backup, SAV commands
I am having to tweak my All User Data save job to omit certain files from the save. I'm unsure of the proper naming convention for the save. The call currently looks like this.SAV DEV(tap03) OBJ(('/*') ('/QSYS.LIB' *OMIT) + ('/QDLS' *OMIT) ('/QIBM/ProdData' *OMIT) + ('/QOpenSys/QIBM/ProdData' *OMIT)) + UPDHST(*YES) Would my next omit statement for a file in a library look like ('/LIBNAME/FILENAME' *OMIT)

Software/Hardware used:
ASKED: September 30, 2008  4:56 PM
UPDATED: August 12, 2010  6:42 AM
RELATED QUESTIONS
Answer Wiki:
Assuming the file(s) you want to omit are in the IFS, you can add ('/dirname/filename.ext' *OMIT) to the OBJ( ) group - or - you can use PATTERN(('filename.ext' *OMIT)) or PATTERN(('*.ext' *OMIT)) to omit all files matching this pattern that would reside in the Included paths. The pattern is not case sensitive.
Last Wiki Answer Submitted:  October 1, 2008  4:28 pm  by  Mid11   80 pts.
All Answer Wiki Contributors:  Mid11   80 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

 

Here is a example of the SAV command we run nightly which does what you asked:

SAV DEV(‘/QSYS.LIB/TAP01.DEVD’) OBJ((‘/home/*’ +
*INCLUDE) (‘/home/atlantis/**.mdl’ *OMIT) +
(‘/home/atlantis/journal/*’ *OMIT) +
(‘/home/atlantis/adel/pr_hr/**.mdl’ +
*OMIT) +
(‘/home/atlantis/carter_holt_harvey/**.mdl’ +
*OMIT) +
(‘/home/atlantis/controllers/**.mdl’ +
*OMIT) + (more parms here)

Notice the **.mdl This causes the command to skip all objects with the .mdl extension.
A single asterisk will not work for this purpose. It is interpreted differently by the command processor.

WoodEngineer
 5,525 pts.
 

For a user library, the full path name would be /QSYS.LIB/LIBNAME.LIB/FILENAME.FILE. This is because, in the IFS, the QSYS library contains all the other libraries. Also, each object name has a suffix to identify what type of object it is, i.e., .FILE, .LIB, .CMD, .PGM, etc.

Cwc
 4,275 pts.
 

This is because…

For just a little more detail, the first node of a path is the name of the file system. Libraries exist in the QSYS.LIB file system. Therefore, the path begins with /QSYS.LIB.

Libraries are containers, so they are specified similarly to directories. Therefore, the next node in the path is /LIBRARYNAME.LIB — the .LIB extension is needed because different object types can share the same name.

Database files are also container objects and specified similarly to directories. The third node is then /FILENAME.FILE — the .FILE extension again identifies a unique object.

In any case, the /QSYS.LIB node is the file system identifier. /QDLS and /QOpenSys are two other file system examples. All file systems are part of the IFS (Integrated File Systems).

Tom

TomLiotta
 108,055 pts.