"Q" libraries (IBM) libraries on the iSeries
If you see others on your system not on this list, type DSPSFWRSC *PRINT and review the spool file for the fifth column over, which will contain the library name associated with the program product on the system.
QDCT | Is for any language lookup and purpose. DSPSFWRSC will show which languages you are using. |
QDOC | Client access, file transfer, infoseeker will place objects there. If customer not sure what they have created in QDOC, recommendation is do not alter. |
QDSNX | Per document 5125505, it is considered a "user library"; its purpose is to send files back and forth from a mainframe. To link to 5125505 immediately, click here |
QFNTCPL | It has 240 compatibility fonts in it, option 8 of OS/400 is Advanced Function Compatibility Fonts. *IPDS printers need these fonts. WRKDEVD *PRT would show a customer if they have any *IPDS printers. FAX400 needs QFNTCPL. |
QGDDM | Printer Graphics is option 14 of OS/400 to install. *IPDS fonts need graphics fonts. |
QGPLTEMP | Do not recommend delete. Response from install developer was that there are internal objects in here we may not see. Created at install time. |
QGY | This is used for Operations Navigator or Graphical Operations. Do not delete. |
QHTTP | Used only when you are using TCP/IP to designate the AS/400e or iSeries 400 system to do Hypertext Transfer Protocol, to serve multimedia objects to WorldWide Web clients through the internet. It is created at install and is documented in Chapter 13 of the TCP/IP Reference. |
QIWSPS | This is 5763XB1, Licensed Program for Client Access Extended DOS-SBCS-single byte character set. |
QMPGDATA, QMPGLIB | Used for sending performance data to IBM. |
QPDP | This is a 9406 problem analysis, determination library for CISC (R310, R320). It is needed by the system and should not be removed. It is option 10 of Base 5763SS1. |
QPFRDATA | Performance data library. Can do CLRLIB QPFRDATA, then STRPFRMON will get everything going again. |
QPWXCGY | Client Access/400 GraphicOps for Windows. Option 6 of 5763XC1. |
QPWXCPC | Client Access Windows 3.1 PC5250. Corresponds to option 5 of 5763XC1. |
QQALIB | This is the Question and Answer library, created at install time. |
QRUMBA, QRUMBAD, QRUMBA2 | Can view via DSPSFWRSC, then F11. QRUMBA AND QRUMBAD are part of 5763XB1, Client Access/400-Extended DOS RUMBA SBCS and Client Access/400-Extended DOS RUMBA DBCS. QRUMBA2 is Client Access/400-OS/2 RUMBA SBCS. |
QSRV | This is the System Service Library, created by *IBM and is used temporarily for PTFs and APARs during PTF processing; is normally empty. It should not be deleted. |
QUPGRADE | Purely a migration library. If migration is successful, can be removed via DLTLIB. |
QUSRINFSKR | For Infoseeker/Bookmanager product. If Infoseeker is to be viewed via CD-ROM only then this may be removed; is not very big though. To remove Infoseeker shelves from system, do a DLTFLR QBKBOOKS/BOOKS, then set up QBOOKPATH system value to point to CD-ROM only, for example, for R410 system QBOOKPATH is defined on page 4-7 of Softcopy Library CD-ROM, publication SK3T-0118-00. |
QUSRTEMP | Library created at install time; should not be deleted. It is used at install/reinstall time to move objects back and forth while comparing them to OS/400 programs in QUSRSYS, for example, QASXPROB, the problem log. Functions such as QSNADS AND QSPL (sending files between AS/400e or iSeries 400 systems, starting printers), need to see this library and have authority to it, to execute without error. |
QWSG | This library is created at install time of OS/400. Used for configuring Workstation Gateway Server between the AS/400e or iSeries 400 system and the Internet. This allows the AS/400e or iSeries 400 system and the Internet to send 5250 Data streams as Hypertext Markup Language for dynamic display on Web Browsers. |
IBM ships the i5 with some libraries already installed. All IBM-supplied libraries have names beginning with the letter Q. The reverse (all libraries that have names beginning with Q are IBM's) is not necessarily true because you can use the Create Library (CRTLIB) command to create a user library and give it any name you want (even if it begins with Q). However:
Do not give your own libraries names beginning with the letter Q. You can name objects any way you want (even with Q at the beginning), but if you adopt the practice of beginning your object names using letters other than Q, it will be easier to distinguish IBM's objects from your own.
Never, under any circumstances, delete an IBM-supplied library using the Delete Library (DLTLIB) command. If you absolutely have to get rid of one of them, you should treat the process as a deinstallation of a licensed program. Run the GO LICPGM command to get to the Licensed Programs menu, then select the option that deinstalls them. The system presents a list of all licensed products currently installed. Enter option 4 next to the item you want to delete and press Enter twice. You do not need a dedicated system to perform this task.
The rest of this section contains a brief description of some of IBM's libraries.
QSYS
QSYS is the most important library in the system. QSYS contains the operating system, and it also contains all other libraries. You cannot operate the computer without QSYS.
Several types of objects cannot be placed anywhere but in QSYS. Three examples are user profiles, device descriptions, and authorization lists.
QSYS has a number of unusual traits. You cannot save it using the Save Library (SAVLIB) command or restore it using the Restore Library (RSTLIB) command. You cannot save any of its objects using the Save Object (SAVOBJ) or Save Changed Objects (SAVCHGOBJ) command. Consequently, you cannot restore it using Restore Object (RSTOBJ) either.
| Tip | You should never, under any circumstances, delete objects from QSYS. The various Delete (DLTXXX) commands will not stop you if you have enough authority, but the result could be disastrous. You cannot save or restore QSYS objects. The only way to save QSYS is by running the Save System (SAVSYS) command. Except for a few exceptions, you cannot restore any QSYS objects except by reloading the entire operating system over again. |
You can delete QSYS objects only if specialized commands exist for that purpose. For example, user profiles always reside in QSYS. You can delete user profiles (even though they are in QSYS) because a Delete User Profile (DLTUSRPRF) command is available. You must use the specialized command to perform the deletion.
On the other hand, no specialized command exists to delete a file from QSYS. The Delete File (DLTF) command is generic for all libraries.
| Tip | Never, under any circumstances, create one of your own objects into QSYS or move one of your own objects from any library into QSYS. Leave QSYS for IBM-supplied objects. |
QUSRSYS
QUSRSYS is a library in which you can place user objects and still consider them, more or less, "system" objects. Typically, QUSRSYS contains message queues for user profiles and some data files used by the system (which you can delete in most cases). QUSRSYS, however, is a "normal" library. You can save it and restore it (as well as its contents) in the normal fashion.
QHLPSYS
QHLPSYS contains all the help information (which is extensive) that is provided by the system at the touch of the Help key. QHLPSYS contains most of this information in the form of panel group and search index objects.
QHLPSYS is not essential to run the system if you don't mind not having help available. The system-supplied help support is so convenient, however, that it is easy to take it for granted.
QGPL
QGPL's name stands for General Purpose Library. As this name implies, QGPL contains a potpourri of miscellaneous objects that can be used either by the system or by you at various times. QGPL contains objects such as job queues, subsystem descriptions, source physical files, and output queues.
QGPL should not be cluttered with user objects. Do not use it to store your own objects unless there is a compelling reason to do so. Keep this advice in mind whenever you create an object.
Table 19.1 lists some other system libraries and gives a brief description of each of them. A complete list is found in Appendix C of the CL Programming manual (SC41-5721-06).
| Tip | Most Create (CRTXXX) commands default the library to *CURLIB (whatever library happens to be your current library). However, if you don't have any library as current, the object is placed in QGPL. |
Open table as spreadsheetLibrary | Description |
|---|---|
QCCA | CCA cryptopgraphic service provider |
QCLUSTER | DB2 multisystem |
QDNS | Domain name system |
QFNTCPL | AFP* compatibility fonts |
QFNTWT | Additional fonts |
QFPNTWE | NetWare enhanced integration |
QGDDM | Support for graphical data display manager and presentation graphics routines |
QICSS | Digital Certificate Manager |
QICU | International components for Unicode |
QIWS | Host servers |
QJRNL | High availability journal performance |
QMSE | Media and Storage Extensions (MSE) library |
QPASE | Portable app solutions environment |
QPFRDATA | Library of system-collected performance data |
QQALIB | Question-and-answer utility library |
QRCL | Library for reclaiming objects via the RCLSTG command |
QRECOVERY | System recovery library |
QRPLOBJ | Library for replaced objects |
QSC xxxxxxx | Data library for collecting APAR data; xxxxxxx = last 7 digits of the problem identifier |
QSHELL | Qshell interpreter |
QSMP | DB2 symmetric multiprocessing |
QSOC | OptiConnect |
QSPL | Spooling library |
QSR | Object Connect |
QSRV | System service library |
QSYSCGI | System CGI Program Library |
QSYSDIR | Extended base directory support |
QSYSINC | System openness includes |
QSYSLOCALE | Contains locale source members for use in creating *LOCALE objects. |
QSYSNLS | Extended NLS support |
QSYSVxRxMx | iSeries CL compiler library, previous release support; x identifies the version, release, and modification level of the previous release |
QSYS2 | Supplemental system library for objects whose names do not begin with the letter Q; includes, for example, objects for CPIs. |
QTEMP | Temporary library of user |
QUSRTEMP | Not shipped with system; created at install time |
QUSRTOOL | Example tools |
Product Libraries
IBM-licensed program products are self-contained software packages. Each comes in a separate library (a product library).
For example, the Application Development Tools program product, also known as PDM (Program Development Manager), comes in library QPDA. The RPG/400 compiler and RPG/400 support come in library QRPG.
Related Articles
Restore a library
RSTLIB, F4Creating a Task Library
Now, all Admins have the ability to add tasks to a “Task Library”. To access your library, go to “Settings->Advanced->Task Library”, located on the left sidebar of your dashboard. Click “Add New Task” to add a new task to your “Task Library”. Please ...Configure iSeries Access Printer
Adding a iSeries Access printer session to a computer Click on Start, programs, IBM iAccess for windws, emulator, Start or configure session. Depending on the version of iSeries access, click “New Session” or “Configure” Note below: Name of ...Checking Version, Release and Service Pack level of iSeries Access
Checking Version, Release, Service Pack Level of iSeries Access for Windows Click Start, Programs, IBM iAccess for Windows or iSeries Access for Windows Click on “IBM iAccess for Windows Properties” Read the second line down on the screen that ...How to check the system connection name in iSeries Access
In the iSeries Access session, click on Communication, configure, the system name appears there: As above, it could be a DNS name. As above, it could be an IP address. As above, it could be IP address at SAS.