question about filesystems
igor....@gmail.com
Could someone help me fill this out:
QSYS.LIB - database filesystem
QDLS - user docs FS
QNTC - ?
QOPT - ?
QFileSvr.400 - ?
QSR - ?
IFS - ~ unix FS
- QIBM, bin, dev, usr, opt ...
I was looking for this info on IBM iSeries Info Center, but haven't
found everything...
Thank you,
Igor
Elvis
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/ic2924/info/ifs/rzaaxfsknow.htm
QSR - don't know what that is, perhaps a user defined file system
(UDFS)?
QIBM,bin,dev,user,opt - these are subdirectories in root, not file
systems.
igor....@gmail.com
dkahn400
> QSYS.LIB - database filesystem
> QDLS - user docs FS
>
> QNTC - ?
> QOPT - ?
> QFileSvr.400 - ?
> QSR - ?
>
> IFS - ~ unix FS
> - QIBM, bin, dev, usr, opt ...
>
> I was looking for this info on IBM iSeries Info Center, but haven't
> found everything...
QSYS.LIB - Library file system (Library and traditional i5/OS object
access)
QDLS - Document library services file system (Document and folder
access)
QNTC - iSeries NetClient file system (Windows NT Server access)
QOPT - Optical File System (Access to files stored on Optical media)
QFileSvr.400 - OS/400 File Server file system (File system access in
remote iSeries systems)
QSR - Sorry, can't help there.
> IFS - ~ unix FS
Not really. The IFS (Integrated File System) is the entire hierarchical
structure of all the file systems, including QSYS.LIB. The root file
system (a simple /) provides the UNIX-like directory structure for
stream files and the tree of directories that contain them.
Don't forget also:
QOpenSys - Open systems file system (Case-sensitive directory and
stream file access)
QNetWare - NetWare file system (Novell Netware Server access)
--
Dave...
BigG
which includes database, COBOL, RPG, CL,and "C" programs (most programs
except Java), commands, native objects (like JOBQs, Subsystems, Message
Queues, etc.), - basically, anything that's in a native OS/400 library. So
because of this, names can only be 10 characters long (before the
"extension," which is a "canned" extension name that IBM came up with for
each OS/400 object type). For example, an OS/400 program would be
/QSYS.LIB/TEST.LIB/PGMA.PGM and data in a file would be
/QSYS.LIB/TEST.LIB/FILEA.FILE/FILEA.MBR
/QDLS is user docs, but it's kind of outdated and not used much anymore.
Anything under this directory uses the old "DOS" naming convention of 8
character filename with a three character extension.
Most people now use their own directory under '/' (any directory off the
"root", or "/" that isn't one of these "special" ones will be
case-insensitive long file names, similar to Windows). These "root" level
directories are supposed to be more efficient than /QDLS.
/QOPT is for any optical disk you have, or for any CD ROM or DVD drives. If
the drive is active on the system and you have media in it, the files will
appear under /QOPT without having to do any "mount" command.
Not sure about some of the other ones you mentioned, but another one you
should know about is /QOpenSys.
/QOpenSys is the UNIX-style file system with case sensitive long names.
This is also where you would put any AIX binaries that you wanted to run in
PASE (Portable Application Soloutions Environment).
IFS stands for "Integrated File System" which is really the whole thing....
The IFS includes /QSYS.LIB, /QOPT, /QOpenSys, QDLS, and the "root" file
system ('/'). However, many times people may refer to anything not in
/QSYS.LIB to be "the IFS" because /QSYS.LIB is thought of as the "native"
OS/400 file system and "the IFS" is everything else. That's not technically
correct because in actuality, "the IFS" includes /QSYS.LIB along with "root"
and all the other file systems.
Hope this helps give you a background for your reading....
<igor....@gmail.com> wrote in message
news:1126849396.7...@g14g2000cwa.googlegroups.com...
Igor Lautar
<cut>
Thank you all for great answers. The one that is bothering me is /QSR
filesystem. SAV doesn't want to save it, at least if it is empty, and it
doesn't specify the reason why.
i.e.:
SAV OBJ(('/QSR')) DEV('/QSYS.LIB/SOMELIB.LIB/TEST_SAV.FILE')
OUTPUT('/tmp/sav_data') INFTYPE(*ALL)
I get:
Message ID . . . . . . : CPC3715 Severity . . . . . . . : 00
Message type . . . . . : Completion
Date sent . . . . . . : 09/16/05 Time sent . . . . . . :
09:56:45
Message . . . . : No objects saved, all objects were excluded.
Cause . . . . . : Objects were excluded from the save for the following
reasons:
-- 0 objects were excluded because they did not meet the requirements
specified on the CHGPERIOD parameter.
-- 0 objects were excluded because they were omitted using the *OMIT
value
on the OBJ parameter.
-- 0 objects were excluded because they did not meet the requirements
specified on the SYSTEM parameter.
-- 0 objects were excluded because they did not meet the requirements
specified on the ASPDEV parameter.
-- 0 objects were excluded because they did not meet the requirements
specified on the PATTERN parameter.
Processing /tmp/sav_data gives record specifying end of save list (so SAV
does not report /QSR as being saved). And as you can see, there is no
reason listed why object would be excluded (one explanation would be that
one cannot save mount points since the same thing happens with QNTC, QOPT
and some others).
If empty dir is, for example, /tmp/empty_dir, SAV saves this dir as empty
(and I can restore it using RST).
Regards,
Igor
Dave McKenzie
Save/Restore function of the OS. Besides the one in the root (/QSR)
they sometimes occur at lower levels (e.g. /QOpenSys/QSR).
They aren't saved because they have the "Can be saved" attribute set to
"No" (WRKLNK, option 8, last page).
--Dave
Igor Lautar
Dave McKenzie wrote:
> I think QSR directories are some kind of work areas used by the
> Save/Restore function of the OS. Besides the one in the root (/QSR)
> they sometimes occur at lower levels (e.g. /QOpenSys/QSR).
>
> They aren't saved because they have the "Can be saved" attribute set to
> "No" (WRKLNK, option 8, last page).
This is exactly what I was looking for.
Thank you,
Igor