Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Files, modules and procedures used by IQS

&pagelevel(3)&pagelevel

Figure 12: Interaction of IQS, UDS/SQL and operating system

C.IQS

IQS load module for independent DBH

C.L.IQS

IQS load module for linked-in DBH

IQSMAIN

IQL processor program, executable as shareable code in class 4 or class 5 memory (see the "Subsystem Management in BS2000” manual). IQSMAIN is loaded automatically by IQS from the module library SYSLNK.IQS.040. Its main memory requirement is approx. 188 Kbytes.

IQSGERM
IQSENGL

IQL language modules containing the IQL messages/error messages. The modules are reloaded from SYSLNK.IQS.040 and can be held in class 4 or class 5 memory.

IQS#.tsn.STANDARD

Temporary work file (user file) which is automatically created when the FIND command is used and deleted again when the IQS session terminates normally. If termination is abnormal, the file must be deleted with the DELETE-FILE command.

IQS.LOGFILE.tsn

Log file which receives IQS session logs.

SYSPRG.IQS.040

Library which contains the IQS load modules.

SYSLNK.IQS.04

Object module library which includes the IQL processor program IQSMAIN.

IQS.PRC.START

Start procedure for IQS. This procedure is contained in the library SYSPRC.IQS.040.

IQS dynamically loads the object modules it requires for UDS/SQL from a library which is assigned with the link name UDSOML via the ADD-FILE-LINK command.

/ADD-FILE-LINK LINK-NAME=UDSOML,FILE-NAME= ...,

The other connection modules of the independent DBH or the linked-in-DBH are dynamically loaded as with other application programs (see the “Application Programming” manual).