UNIDATA System Debug Toolkit User's Guide openCTOS4 Software Additional copies of this document can be ordered through your branch representative or from UNIDATA (Pty) Ltd.; CTOS Focus Group (Innovative Technology), PO Box 47178, Parklands 2121, Republic of South Africa. CTOS Focus Group R&D Section (NT) System: + B/CTOS Style Number: + OC25-WA Version: + 12.03 NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product and related material disclosed herein are only furnished pursuant and subject to the terms and conditions of a duly executed Program Product License or Agreement to purchase or lease equipment. The only warranties made by UNIDATA, if any, with respect to the products described in this document are set forth in such License or Agreement. UNIDATA cannot accept any financial or other responsibility that may be the result of your use of the information or software material, including direct, indirect, special or consequential damages. You should be careful to ensure that the use of this information and/or software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used. The information contained herein is subject to change without notice. Revisions may be issued to advise of such changes and/or additions. The names, places, and/or events used in this publication are not intended to correspond to any individual, group, or association existing, living, or otherwise. Any similarity or likeness of the names, places, and/or events with the names of any individual, living or otherwise, or that of any group or association is purely coincidental and unintentional. TRADEMARKS: BTOS, CTOS are trademarks of UNISYS Corp. UNIX is a trademark of AT&T. openCTOS is a trademark of Special Systems Group, Datakor Holdings (Pty) Ltd. Nepsof Technologies is a trademark of Special Systems Group, Datakor Holdings (Pty) Ltd. UP Technologies is a trademark of Special Systems Group, Datakor Holdings (Pty) Ltd. Spectra Focus is a trade mark of SpectraFocus, Cape Town. Contents Section 1 General Description 7 Section 2 New Release Functionality 9 Changes from Prior Releases 9 General Functionality 9 openCTOS Debug ToolKit Features 9 Miscellaneous Enhancements 10 Section 3 Product Interdependencies 11 System Software Compatibility 11 openCTOS Environment 11 Workstation Environment 11 SRP Environment 12 Hardware Information 12 Hardware Configurations Supported 12 Special Hardware Requirements 12 Resource Requirements/Utilization 12 Memory Requirements/Utilization 12 Table 1-1. Memory Utilization 13 Disk Requirements/Utilization 14 Table 1-2. Disk Utilization 14 Supplementary Information 15 Invoking openCTOS Debug ToolKit 15 Example Of Pass-One RqRsp Trace (Simple Trace) 21 Example Of Pass-Two RqRsp Trace (Detail Trace) 22 Example Of Stat Trace 23 General Hints 24 Section 4 Migration Requirements 25 Compatibility with Previous Versions 25 Compatibility Issues Specific to openCTOS 25 Common Compatibility Issues 25 Section 5 Corrections 27 UCFs Closed in This Release 27 Section 6 Restrictions and Known Limitations 29 Restrictions 29 Known Errors and Omissions 29 Section 7 Support 31 Support Category 31 Support Discontinuance 31 Support Contact 32 Section 8 List of Files on Product Media 33 Contents of the Distribution Diskettes 33 Section 9 Installation Procedure 35 Local Installation of openCTOS Debug ToolKit 36 Required Files 37 Section 10 Error Codes 39 Section 11 Glossary 41 Section 12 User's Comment Sheet 57 Section 1 General Description This Software Release Announcement describes the current release of openCTOS Debug ToolKit . This section and the sections that follow provide a description of the product, contents of the Distribution Diskettes, installation procedures, and other information pertinent to this release of openCTOS Debug ToolKit. This version of openCTOS Debug ToolKit represents the merger of the UNIDATA product, openCTOS, with the Nepsof Technologies product RqRsp Watchdog. Instructions on how to use openCTOS Debug ToolKit are given later in this User's Guide. Section 2 New Release Functionality Changes from Prior Releases General Functionality openCTOS Debug ToolKit consists of an application and system service option, each of which is intended to trace and format request and response traffic. The RqRsp Service offers a high speed trace functionality. openCTOS Debug ToolKit Features The following capabilities of openCTOS Debug ToolKit are new to users of Debug ToolKit 12.0 . 1. Statistics: The RqRsp Formatter can be supplemented with the Spectra Focus Stastistics Reporter, which displays a statistics of the request/response traffic if option massIO is used. 2. Multi File: The watchdog service now supports a multiple of trace files and will automatically close and open next trace file if a file full situation occurs. 3. Multi Enable/Disable: The trace session can be enabled and disabled more than once and with each enable a new trace file will be created. 4. Error Display: All request and response blocks which contain an ercRet other than zero (0), are marked with three asterix characters .. ***. Miscellaneous Enhancements The overall performance of the openCTOS Debug ToolKit software has been improved, by major rewrites and redesigns of the internal core logic. P WARNING P openCTOS RRP Monitor product has been discontinued and is not part of th2 12.03 release. Section 3 Product Interdependencies System Software Compatibility openCTOS Environment openCTOS Debug ToolKit is qualified with openCTOS Common Service software openCTOS 12.3 or higher. CAUTION openCTOS Common Service Software must be installed before any part of the openCTOS Debug ToolKit is executed on the local system. If the openCTOS Common Service Software is not available the openCTOS Debug ToolKit software will fail with error 7. (Not Implemented). Workstation Environment openCTOS Debug ToolKit is only qualified for protected mode operation and requires BTOS II 3.4 or higher or CTOS III-1.0 or higher. SRP Environment The current releases of openCTOS Debug ToolKit services have not been qualified on SRP based systems. Hardware Information Hardware Configurations Supported openCTOS Debug ToolKit is supported on the following workstations: CWS NGEN 286 B28 B28-EV B28-EXP 386 B38 B38-EV B38-EXP B39 SG 2000 5000 Special Hardware Requirements The features of openCTOS Debug ToolKit are supported on all disk devices and floppy devices. Resource Requirements/Utilization Memory Requirements/Utilization No special requirements. The following table details the memory requirements. Table 1-1. Memory Utilization  Service Type of Installation Memory (kb)  openCTOS RqRsp Watchdog Standard installation 50 per Cache Buffer +65 openCTOS RqRsp Utility Standard installation 40 openCTOS RsRsp Format Standard installation 80 openCTOS RsRsp Stats Standard installation 180 openCTOS RRP Monitor Standard installation 200  Disk Requirements/Utilization The following table details the disk requirements. Table 1-2. Disk Utilization  Package Sectors  openCTOS RqRsp Watchdog 84 openCTOS RqRsp Utility 77 openCTOS RsRsp Format 164 openCTOS RsRsp Stats 135 openCTOS RRP Monitor 434  Supplementary Information Invoking openCTOS Debug ToolKit openCTOS Debug ToolKit can be invoked from the Executive, from Batch Manager by adding the installation commands into the sysinit.jcl installation file. The Batch Manager installation is the preferred version of installation. To install the openCTOS RqRspWatchDog service select the command: Command /RqRsp Watchdog RETURN [Number Of Cache Buffers] [Print File] [Request Codes] [Number Of Outstanding Requests] [Max Buffer Trace Size] [File Size] [Auto Trace] 1. Number Of Cache Buffers: Defines the number of internal trace buffers that the service should allocate for write ahead caching. The more buffers the faster the processing. The number is limited between 2 and 5, while the default is 5. 2. Print File: Defines the file into which the raw trace will be written. This trace is unreadable until it has been formatted by the formatting utility. Be aware that the service automatically appends the string ".nnnnn" to the file name, where nnnnn is the trace sequence number ranging from 1 to 65535. 3. Request Codes: Up to 15 request codes to be traced by the service. The request codes can be entered as decimal numbers, i.e. 50, or hexadecimal number by suffixing the number with "h", i.e. 32h. A special token massIO can be used in place of actual request numbers, which will automatically trace all relevant file i/o requests: openFile, openFileLL, reOpenFile, readFile, writeFile, closeFile, closeAllFiles, closeAllFilesLL, getFileStatus, setFileStatus and changeFileLength. 4. Number Of Outstanding Requests: Defines the maximum number of outstanding requests that the service can cater for. The default is 500, whereby the valid range is from 250 - 5000. 5. Max Buffer Trace Size: Defines the maximum size of the data buffer which is actually traced from the request blocks. The maximum size is 65535 bytes, whereby the size should be kept to a minimum, both to reduce the final trace file size and to avoid major overhead. Default is 2048 bytes per pbcb pair. 6. Trace File Size: The maximum trace file size. Once the file is full the service will disable trace mode and beep continuously to alert the user. The maximum size is disk bound, whereby the default file size is 999936 bytes. It should be a multiple of the number of cache buffers, multiplied by 0FFFFh, plus 2 sectors. 7. Auto Trace: By default the service will not start tracing until the service is commanded to start tracing. By setting this parameter to "Yes", the service will start tracing immediately. 8. Maximum No Files: defines the maximum number of trace files to be created by the service, ranging from 1 - 65535, whereby the service will start tracing from one again, should all files get full. To install the openCTOS RqRsp Formatter utility select the command: Command /RqRsp Formatter RETURN [Input File] trace.tmp [Output File] trace.fmt [Simple Report Only] [Supress Unknowns] [Page Size (66)] [Format User # Only] [# 1 Rq, Name] .... [# 15 Rq, Name] 1. Input File: Defines the input file which contains the raw trace. 2. Output File: Defines the output file into which the formatted trace file will be written. 3. Simple Report only: If set to "Yes" the formatting utility will only produce a simple request response flow report, not including any request block specific information or actual data. 4. Suppress Unknowns: If the formatting utility detects any request it has not been informed about, it marks it as unknown. If this parameter is set to "Yes" the formatting utility will not include unknown requests in the final report. 5. Page Size: Actual page size out the output report. Default is 66 lines. 6. Format User # Only: By default the formatting utility processes all requests within a specific raw trace. If the user specifies a unique user number only the requests for that user will appear in the final trace. 7. # 1-15 Rq, Name : The 15 parameters define the actual request code and the name that the formatting utility should use for each in the report. The codes must match the codes which were defined when installing the watchdog, else unknowns will occur. If massIO was used when installing the service, the first parameter can be set to massIO, after which the utility will automatically allocate the request codes and the specific request names. To install the openCTOS RqRsp Stats Formatter utility select the command: Command /Rq File IO Statsr RETURN [Request Trace File] trace.raw [Print File] trace.sta 1. Input File: Defines the input file which contains the raw trace. 2. Print File: Defines the output file into which the formatted statistics trace file will be written. To disable the openCTOS RqRsp Watchdog service, which will stop any active tracing without deinstalling the service, select the command: Command /RqRsp Disable GO To enable the openCTOS RqRsp Watchdog service which will stop any active tracing without deinstalling the service, select the command: Command /RqRsp Enable GO To deinstall the openCTOS RqRsp Watchdog service select the command: Command /RqRsp Deinstall GO To query the openCTOS RqRsp Watchdog service select the command: Command /RqRsp Query Stats GO To install the openCTOS RRP Monitor utility select the command: Command /RRP Monitor GO Once you are in the RRP Monitor main menu, you can select any option. The first option should be to configure the environment, unless you have edited the RRPConf.sys configuration file which is used as a default template. Be careful when editing the configuration file and ensure that you adhere to all instructions within the configuration file. The file must be edited with the standard CTOS Editor. As the utility offers on-line help and as this product will be completely replaced by the RqRsp Services in future releases, this document will cover no further functionality or options offered by the RRP Monitor. Example Of Pass-One RqRsp Trace (Simple Trace) Report Generated By : Dated : Tue Feb 4, 1992 2:33 PM Trace Buffer Size : 02048 Bytes Trace Started : Tue Feb 4, 1992 2:31 PM Trace Finished : Tue Feb 4, 1992 2:32 PM Request Information : openFile {00004 |00023h Rq's 00023h Rsp's 0005h Erc's |} openFileLL {00097 |00000h Rq's 00000h Rsp's 0000h Erc's |} reOpenFile {00294 |00000h Rq's 00000h Rsp's 0000h Erc's |} readFile {00035 |0029Bh Rq's 0029Bh Rsp's 0001h Erc's |} writeFile {00036 |00008h Rq's 00008h Rsp's 0000h Erc's |} closeFile {00010 |00019h Rq's 00019h Rsp's 0000h Erc's |} closeAllFiles {00019 |00007h Rq's 00007h Rsp's 0000h Erc's |} closeAllFilesLL {00062 |00000h Rq's 00000h Rsp's 0000h Erc's |} getFileStatus {00008 |0000Fh Rq's 0000Fh Rsp's 0000h Erc's |} setFileStatus {00009 |00000h Rq's 00000h Rsp's 0000h Erc's |} changeFileLengt {00013 |00000h Rq's 00000h Rsp's 0000h Erc's |} Pass One Formatting .. REQUEST TRAFFIC RESPONSE TRAFFIC 00001 readFile (020492 14:31:36:008) 0001 readFile (020492 14:31:36:008 erc 000) 00002 readFile (020492 14:31:36:008) 0002 readFile (020492 14:31:36:008 erc 000) 00003 openFile (020492 14:31:36:008) 0003 openFile (020492 14:31:36:008 erc 000) 00004 getFileStatus (020492 14:31:36:008) 0004 getFileStatus (020492 14:31:36:008 erc 000) 00005 readFile (020492 14:31:36:008) 00006 readFile (020492 14:31:36:008) 0005 readFile (020492 14:31:36:008 erc 000) 0006 readFile (020492 14:31:36:009 erc 000) 00007 openFile (020492 14:31:36:009) 0007 openFile (020492 14:31:36:009 erc 203) *** 00008 getFileStatus (020492 14:31:36:009) 0008 getFileStatus (020492 14:31:36:009 erc 000) Each request and response is marked with a unique sequence which can be used to identify the corresponding response within the trace and enable one to find the relevant request and response block in the detailed trace. NOTE The report has been edited to fit the width of this user's guide. The actual trace is wider and therefore clearer to read and analyze. Example Of Pass-Two RqRsp Trace (Detail Trace) Pass Two Formatting .. REQUEST TRAFFIC RESPONSE TRAFFIC 00003 openFile (020492 14:31:36:008) Header | 06 00 02 01 19 00 81 00 00 00 04 00 | CntInfo | 00 00 70 6D 00 00 | pbcb00 | 7C48:AD20 0012 | |5B7379735D3C7379733E7379|[sys]sy| |732E636D6473 |s.cmds | pbcb01 | 7C48:AD00 0008 | |636176656469736B |cavedisk | 0003 openFile (020492 14:31:36:008 erc 000) Header | 06 00 02 01 19 00 81 00 00 00 04 00 | CntInfo | 00 00 70 6D 00 00 | Pbcb00 | 7C48:AADC 0002 | |0200 |.. | 00004 getFileStatus (020492 14:31:36:008) Header | 06 00 00 01 19 00 81 00 00 00 08 00 | CntInfo | 02 00 00 00 00 00 | 0004 getFileStatus (020492 14:31:36:008 erc 000) Header | 06 00 00 01 19 00 81 00 00 00 08 00 | CntInfo | 02 00 00 00 00 00 | Pbcb00 | 7C48:FF9E 0004 | |00400300 |.@.. | NOTE The report has been edited to fit the width of this user's guide. The actual trace is wider and therefore clearer to read and analyze. Example Of Stat Trace FILE STATISTICS : Sample for period 02/04/92-02:31:34PM to 02/04/92-02:32:50PM 35 Requests / 35 Responses : Request Code 4 OPENFILE 667 Requests / 667 Responses : Request Code 23 READ 8 Requests / 8 Responses : Request Code 24 WRITE 25 Requests / 25 Responses : Request Code A CLOSEFILE 7 Requests / 7 Responses : Request Code 13 CLOSEALLFILES 15 Requests / 15 Responses : Request Code 8 14 reads 0 writes sys.cmds 4 reads 0 writes Cluster.cmds 0 reads 0 writes Undelete.Run 38 reads 0 writes ExecMsg.bin 566 reads 0 writes [sys] 0 reads 0 writes sysimage.sys 0 reads 0 writes Exec.run 3 reads 0 writes ErcMsg.bin 0 reads 0 writes UtilRqRspWatchDog.run 1 reads 0 writes RqRspWatchDog.bin 0019:0001 General Hints * When installing the trace watchdog, thereafter an application which uses requestDirect, rather than request, the application must be terminated before the watchdog is deinstalled. If the watchdog must be terminated before the application, then you have to install the watchdog with auto trace mode disabled and enable tracing once the application has been installed. The problem is caused by the following logical sequence of events: 0 Watchdog installs and serves all specified requests at its own exchange (exchB). All requests will be trapped and forwarded to the actual service exchange (exchA) which initially served the request. 0 The application now installs and queries the service exchange of its requests and will be informed that all requests are served at exchB. 0 The watchdog is now terminated and serves the requests back from exchB to exchA. 0 Applications using the request primitive will have no problem, because the kernel will route the request accordingly. However the application in question will "requestDirect" all requests to exchB, which no longer exists. 8 Application hangs or receives erc33. Section 4 Migration Requirements Compatibility with Previous Versions This version of openCTOS Debug ToolKit is fully compatible with previous levels of Debugger ToolKit Software.. Compatibility Issues Specific to openCTOS This version of openCTOS Debug ToolKit is only supported with openCTOS environments specified in the openCTOS Environment section specified referred to in this document. Use of any other release of openCTOS software may lead to unpredictable system failures. Common Compatibility Issues None. Section 5 Corrections UCFs Closed in This Release The following UCF's are fixed in this version of openCTOS Debug ToolKit 12.02.0000 : UCF # Description -- RqRsp Watchdog hangs if more than 5 cache buffers are specified. -- RqRsp Watchdog frequently crashes or hangs when being deinstalled. -- RqRsp does not allow multiple trace files. -- Trace file is not released by watchdog even if disabled. -- RqRsp spuriously crashes during high-speed or large buffer request/response tracing. -- Watchdog crashes on CTOS III-1.0 systems when GDT protected request blocks are encountered. Section 6 Restrictions and Known Limitations Restrictions None. Known Errors and Omissions None. Section 7 Support openCTOS Debug ToolKit is a warranted UNIDATA software product. Support services for openCTOS Debug ToolKit are offered through the standard support channels and are consistent with the support services offered for the entire CTOS Hardware and Software family of products. The product is neither field repairable nor field modifiable. Refer to your software agreement contract for detailed information in this regard. Support Category The following describes some of the support services available for openCTOS Debug ToolKit. The UNIDATA Support Center (USC) offers a Telephone/Hotline service to assist you with any problem. If you encounter software problems (bugs) you can report them to the USC office or you can complete a User Communications Form (UCF). The UCF must be forwarded to USC for review. UCF status is maintained in the UNISYS PRIMUS system. Support Discontinuance UNIDATA supports the current release level and one level back. Prior levels are not supported. Support Contact Marketing and Support Issues Fax & (27-11) 441-4221 or 4608 EMail ) openCTOS/SA-CFG.Mktg R&D Support Issues Fax & (27-11) 441-4221 or 4608 EMail ) openCTOS/SA-CFG.Develop Section 8 List of Files on Product Media Contents of the Distribution Diskettes The openCTOS Debug ToolKit Distribution Diskettes are your master copies, and have been shipped write-protected. They should not be write-enabled, nor should they be used as working copies. Contents include: MailClock diskette (1/1) Directory install.cmds install.ctrl Install.jcl Directory openCTOS.run Section 9 Installation Procedure openCTOS Debug ToolKit should be used only on UNISYS (or Convergent) B/CTOS Information Processing Systems which are equipped with hard disk, or in clusters where the server is equipped with hard disk. Use the installation procedures described below (after updating the Standard Software revision level, if required). Characters that you must type are shown in boldface. Special keys, such as RETURN and GO, are shown in upper case. Local Installation of openCTOS Debug ToolKit A local installation is used for stand-alone workstations and cluster workstations where it is desired to have the openCTOS Debug ToolKit command and run file installed on that workstation. 1. Sign on with the system volume password if applicable. The openCTOS Debug ToolKit installation gives the user the opportunity to change the path and password. 2. Insert the openCTOS Debug ToolKit Distribution Diskette 1/of11 into drive [f0]. Install the product as follows: 3. From the Executive, use the Installation Manager command to initiate the installation procedure, leaving its parameter fields blank. Press GO. Command Installation Manager RETURN [Non-interactive?] GO This command will initiate a menu driven installation process. From the first menu of options, select Install New Software. The second menu prompts you for your installation source; select Floppy Installation if you are installing from the diskettes or Install from Server if you are installing from a server. The next menu sets the installation defaults; if you are not installing to a server, GO TO STEP 4. If you are installing to a server, select Examine/Change defaults and set public to yes in the installation parameters menu (DO NOT select the verbose option as this will make it difficult to view the messages from the installation process.). Now press GO. 1. Select Continue Installation. If the system volume is password protected, you will be prompted for a password now. 2. The remaining menus will establish your choices as to how the installation is to proceed. The following is a list of menus that appear (the default values are within parenthesis): Continue Installation (Yes): If you have not converted your customized format sets to documents, you may want to terminate the installation and do it later when you are ready. Select No if you want to terminate your installation After these menus, you will not be prompted for any further information; if you are installing from the server the installation will proceed unattended. Required Files openCTOS Debug ToolKit requires the files on the product media. Normally they reside in [Sys] . Their location can be changed if the Sys.cmds file, the Context Manager configuration file, and the .user file are altered to reflect these changed locations. P WARNING P If openCTOS Debug ToolKit Software resides in any directory other than [Sys] the installation is not supported by UNIDATA without prior arrangements. Should it be necessary, however, then all *Bin files must reside in [sys], whereas the run files can reside in any other location. Section 10 Error Codes Most status codes for openCTOS Debug ToolKit are covered in the current status codes documentation. Status codes that are not listed in the Status Codes Manual, or have a special meaning in conjunction with openCTOS, are listed below. None. Section 11 Glossary Abort An exception which is completely unrecoverable, such as stack exception during an attempt to invoke an exception handler. Abort Request Notifies system services that clients have terminated. Upon notification, system services can release resources allocated to the terminating client. ACK An acronym for acknowledgment. Address Translation The process of mapping addresses from one address space to another. Segmentation and paging both perform address translation. Advanced Program-To-Program Communication (APPC) An enhancement to SNA that supports distributed transaction processing. It uses Logical Unit Type 6.2. American Standard Code for Information Interchange (ASCII) A character set code consisting of 7-bit coded characters (8 bits including parity check) for information exchange among data processing systems, data communication systems, and related equipment. Application An application is a program solution to a data processing task. Application Programming Interface (API) The collection of operations or interfaces that an application can use to interface to a given software entity. Asynchronous Asynchronous operation is a procedure, or protocol, that enables a delayed response instead of an immediate response. B28 B28 refers to a protected-mode system built with an INTEL iAPX286 processor. B38 B38 refers to a protected-mode system built with an INTEL iAPX386 processor. B39 B39 refers to a protected-mode system built with an INTEL iAPX386 processor. Batch Manager Batch Manager is an application software system that uses Job Control Language (JCL) statements to execute other applications or jobs. BCD Binary Coded Decimal; a format for representing numbers in base 10. One byte is used for each digit of the number, unlike Packed BCD where one byte is used for each two digits of a number. Bit Bit is the abbreviation for binary digit. It is the smallest possible unit of information, corresponding to a choice between two alternatives. Eight bits usually form the code for a character. Block A block is an area of memory allocated for use by cluster communications. A block is also referred to as a sector. Breakpoint An aid to program debugging in which the programmer specifies forms of memory access which generate exceptions. The exceptions invoke debugging software. Buffer A buffer is a device that provides temporary storage for data. Cache The cache is a temporary storage area, used to store information frequently needed. Cache Flush An operation which marks all cache lines as invalid. Cache Miss A request for access to memory which requires actually reading main memory or disk storage. Call Gate A gate descriptor for invoking a procedure with a CALL or JUMP instruction. CCITT Consultative Committee for International Telegraph and Telephone, an agency of the United Nations. This commitee develops telecommunications standards. CCGI+ An applications programming interface for CTOS that meets the ANSI CGI standard. CFG CTOS Focus Group, UNIDATA, a division of Datakor Holdings (Pty) Ltd, South-Africa. Cluster A cluster consists of one or more workstations connected to a shared resource processor or server workstation. Cluster Card An expansion card for IBM-PC compatible computers that provides cluster communications channels. This card is used to integrate PCs into a CTOS cluster. Computer Graphics Interface (CGI) ANSI standard graphics application programming interface. Code Segment An address space which contains instruction; an executable segment. Coprocessor An extension to the base architecture and instruction set of a processor. The 387TM numerics processor is used to add floating point arithmetic instructions and registers to the 386TM processor. Compatible workstation In this manual, a compatible workstation is any workstation manufactured by UNISYS or Convergent Technologies, Inc. CRC-12 A twelve-bit cyclic redundancy checking scheme which uses X12+X191+X3+X+1 as the generator polynomial.. CRC-16 A sixteen-bit cyclic redundancy checking scheme which uses X16+X15+X2+1 as the generator polynomial. CRC-CCITT A sixteen-bit cyclic redundancy checking scheme which uses X16+X12+X5+1 as the generator polynomial. CTOS A workstation operating system; an umbrella term encompassing all varieties of the BTOS and CTOS operating systems. CTOS/Open The CTOS/Open Advisory Council was formed as a joint effort of manufacturers, reseller, distributors, software developers, hardware developers, and users to establish and promote the CTOS-based architecture as a standard of distributed network computing. Cyclic Redundancy Check An error checking routine that creates a polynomial from the data in a transmission frame. This polynomial is sent as a frame check sequence at the end of the frame. The recipient generates a polynomial from the data received and if the polynomial generated by the recipient matches the polynomial sent as the frame check sequence, the data is assumed to be free of errors. Data volume A data volume is used for data and program storage. Deadlock Also called a deadly embrace, deadlock is the state which results when two or more processes or programs are stopped, each waiting for a response that depends on the other stopped process and/or program. Demand Paging A form of virtual memory management in which a program's linear address space is series of contiguous fixed sized regions called pages. A page is either mapped to physical memory or is marked as not present. Demand paging requires hardware support for mapping linear to physical addresses and for detecting not present pages. Descriptor Table An array of segment descriptors. There are two kinds of descriptor tables: the Global Descriptor Table (GDT) and an arbitrary number of Local descriptor Tables (LDT). Device A device is a physical hardware entity. Printers, Tape, floppy disks and hard disks are examples of devices. Device name A device name is the only element of a device specification. Directory A directory is a collection of related files on one volume. You can protect a directory with a directory password. When you specify a directory name, enclose it in angle brackets, for example . Direct Memory Access Access to memory that does not require processor intervention. A DMA controller in the processor module controls the transfer of data over the X-Bus to the main processor's memory. Directory spec A directory specification consists of a node name, volume name and a directory name. Disk device A disk device is a hardware component used to store data. Disk Extent One or more contiguous disk sectors that compose all or part of a file. Encapsulation (OOPS) Combining a record with the procedures and functions that manipulate it to form a new data type: an object. Extended Binary Coded Decimal Interchange Code (EBCDIC) A character set consisting of 8-bit coded characters. It is the usual code generated by synchronous IBM devices. Exception A forced call to a procedure or a task which is generated when the processor fails to interpret an instruction or when an INT n instruction is executed. Fault An exception which is reported at the instruction boundary immediately before the instruction which generated the exception. File system A file system is a collection of files stored on the same logical disk device. It consists of a volume, directories and files contained within each directory. Floppy disk device A floppy disk device is a mass storage device that uses a flexible mylat disk coated with a substance suitable for recording information in the form of electromagnetic signals. Full file spec A full file specification consists of a node name , volume name, directory name, and file name. I.e. {Node}[Volume]FileName Handler A procedure or task which is called as a result of an exception or interrupt. Inheritance (OOPS) Defining an object and then using it to build a hierarchy of descendant objects, with each dependent inheriting access to all it's ancestors' code and data. Interprocess Communication (IPC) The method by which individual CTOS processes communicate by sending messages (requests) to each other. Interrupt External or internal; an event that interrupts the sequential execution of processor instructions. When an interrupt occurs, the current hardware context is saved. This context save is performed partly by the processor and partly by the operating system. ISAM An acronym for Indexed Sequential Access Method. JCL An acronym for Job Control Language. Job Control Language Job Control Language are statements submitted to Batch Manager for interpretation and execution. Kernel The most primitive and the most powerful component of the operating system. It executes with a higher priority than any process, but it is not itself as process. The kernel is responsible for the scheduling of process execution; it also provides IPC primitives. LDT An acronym for Local Descriptor Table. Layered Elastic Generic Open Objects A set of conceptual standards adopted by the CTOS Focus Group, for software solution development. Loadable Request File A loadable request file is a file containing request definitions for system service(s). Local Descriptor Table A Local Descriptor Table (LDT) is a protected- mode structure in memory that contains descriptors for segments accessible to a run file. The operating system constructs the LDT based on information supplied by the Linker. Logical Unit (LU) A network addressable unit (NAU) through which end users access an SNA Network. Linear Address A 32-bit address into a large, unsegmented address space. If paging is enabled, it translates the linear address into a physical address. If paging is not enabled, the linear address is used as the physical address. Logical Address The number used by application programs to reference virtual memory. This number consists of two parts: a segment selector (16 bits) and an offset (32 bits). The segment selector is used to specify an independent, protected address space (segment). The offset is used as an address within that segment. Segmentation translates the logical address into a linear address. Memory Memory is the main high-speed computer storage area where instructions and data are kept for a program that is running. Method (OOPS) Is a procedure or function welded so tightly to a given type that the method is surrounded by an invisible with statement, making instances of that type accessible from within the method. Procedures inside objects are called methods. Methods process information. Methods are executable code. Multiprocessing Using more than one processor in a system. Multitasking Timesharing a processor among several programs, executing some number of instructions from each. Network Control (NC) A set of commands that handle special situations related to network control, such as notification of a lost subarea (SNA). Network Control Program (NCP) The software that runs in a communications controller, PU.T4 device (SNA). Network Control Program Packet Switching Interface (NPSI) The part of the IBM Network Control Program responsible for handling an interface to an X.25 packet switching network. Network Services (NS) A set of SNA commands that provides session, configuration, maintenance, measurement, and network operator services (SNA). Node name A node is a junction in BNet or CT-Net, such as a standalone, a server or a slave workstation. openCTOS4 An envelope term used for all software solutions developed and supported by the CTOS Focus Group, which is striving for a standardized and open CTOS environment. Overflow A floating point exception condition in which the correct answer is finite, but has magnitude too great to be represented in the destination format. Paging A form of memory management used to simulate a large, unsegemnete address space using a small, fragmented address space and some disk storage. Paging provides access to data structures larger than the available memory space by keeping them partly in memory and partly on disk. Password A password is a string of characters or a word which provides a security measure. Physical Unit (PU) The entity responsible for controlling the resources of a node (SNA). Polymorphism (OOPS) Giving an action one name that is shared up and down an object hierarchy, with each object in the hierarchy implementing the action in a way appropriate to itself. POSRES Positive Response Logic, trademark of NEPSOF Technologies. Primitive A primitive is an operation performed by the Operating System Kernel. Procedure Another term for a subroutine. Protection A mechanism which can be used to protect the operating system and applications from programming errors in applications. Re-Entrant Allowing a program to call itself; recursive. Procedures store the ;processor state on the stack, so they may be reentrant to an arbitrary number of levels. Request A request requests that an operation be performed by an operating system request or by a system service process. Request block A request block is a block of memory provided by a client that contains a special type of message formatted according to specific conventions and used by all Inter-Process Communications to the operating system or system service. Sector Sector is the smallest addressable portion of a track or band on a hard or floppy disk. It consists of 512 bytes. Semaphore A synchronization primitive to coordinate the activities of two or more processes that are running at the same time and sharing information. Server A server is a server workstation, which provides file system, queue management facility and other services to all cluster workstations. Stack Fault A special case of the invalid operation exception which is indicated by a one in the SF bit of status word. Stack Segment A data segment or parts thereof, which is to hold a stack. A stack segment may be expand-down, which allows the segment to be resized toward lower address. Status code A status code reports the success or failure of the requested operation. Synchronous operation Synchronous operation is a procedure or protocol, that requires a response at an exact time. Synchronous Data Link Control (SDLC) A bit-orientated, full duplex data communication protocol used for remote communication in SNA networks. Systems Network Architecture (SNA) The formal definition of IBM data communication networking philosophy. Systems Services Control Point (SSCP) The common control point in a domain, responsible for controlling the resources of a domain (SNA). System disk The system disk is the disk on which the workstation system software is installed. Task Switch A transfer of execution between tasks; a context switch. A task switch saves most of the processor state, unlike the procedure calls, which save only the contents of the general registers. Transmission Control Protocol/Internet Protocol (TCP/IP) The two network protocols over which run FTP and TELNET. Transmission Control protocol is responsible for connection establishment, maintenance, data verification, and relinquishment. Internet Protocol supports TCP protocol by sending and receiving network diagrams. Trap An exception which is reported at the instruction boundary immediately following the instruction which generated the exception calls, which save only the contents of the general registers. Ucf UNISYS Customer Form, which is the standard form with which all problems and/or new feature suggestions are submitted. User number A user number is a 16-bit word that uniquely identifies the program and/or resources associated with a partition. Virtual Telecommunications Access Method (VTAM) The main data communication access method used in SNA networks. Volume A volume is the medium of a disk drive that was formatted and initialized with a volume name, a password and volume control structures. A floppy disk and hard disk are examples of volumes. Volume name The volume name is the second element of a full file specification. Write Through A form of caching in which memory writes load both the cache memory and main memory. X.21 A CCITT specification for the interface between data terminal equipment (DTE) and data circuit-terminating equipment (DCE) for connecting stations to a circuit-switched network. X.25 A CCITT specification for the interface between data terminal equipment (DTE) and data circuit-terminating equipment (DCE) for terminals operating in the packet mode on public data networks. X-Bus The extensible bus used to connect modules on a modular CTOS workstation. XVT Extensible Virtual Toolkit; a software library that provides for windowing applications, one application programming interface that can be used to provide a graphical user interface or a graphical like character mode version of such, across multiple operating system platforms and multiple graphical interfaces. Section 12 User's Comment Sheet We welcome your comments and suggestions. They assist us to improve our documentation material. When reporting comments and/or suggestions please specify the section and page number whenever possible. !  Does this manual provide all the information you need? Is it at the right technical level and what other types of documentation is required? .    Is this manual written clearly? .    Is this manual accurate? .    Are there any errors? .    Name  Date  Title  Phone %  Company  Fax/Dex  Department  E-Mail  Address )  City  Area Code  Country 2 P"PXp xXp7- i OC25-RW OC25-RW i Section Level 1 Level 2 Level 3 Level 4 General Description openCTOS Debug ToolKit OC25-RW Page # General Description OC25-RW openCTOS Debug ToolKit Page # New Release Functionality New Release Functionality Product Interdependencies Product Independencies Product Interdependencies openCTOS Debug ToolKit OC25-RW Page # Product Independencies OC25-RW openCTOS Debug ToolKit Page # Migration Requirements Migration Requirements Corrections Corrections Restrictions And Known Limitations Restrictions And Known Limitations Support Support OC25-RW openCTOS Debug ToolKit Page # List Of Files On Product Media List of Files On Product Media Installation Procedure Installation Procedure Errors Errors Glossary Glossary User's Comment Sheet User's Comment Sheet  <>GZ12FGGHG HG H@ @5!  G H  H H@ 5! GH4,DAD,'A !" % 'P ) +P ,57J GHGHGH@$ @5!YZ[\]`abcGH ",-CDVW]^_#D4DLD_ t"]^ED,,GH.'A !" % 'P ) +P ,567J GHGH )+,7RSTrs H,HTIsJJI H!H! H!H! H HHHG&*,> +FGIikʂʞʲJ HIIkJJJI  H!  H!  H!  H!H! HHH H!H! H!&(HJnp̒J(JJIpJJ H! GH"Q=H! H! H!H! H! H!H!  H! !"$@Bdf$IBJfJJJ H! H! H!H! H!H! H! GH#Q=H! H! 89;bdֽ̰̐JH;IdJJH܈ H! H! H!H! HH &*,H H!H! H!  "-QRTceʂԏטԙʮI"HTIeIHIII &H! %H! $H #H! "H! !HHH  H!H! H -.0Y[f~ٰH0I[HIIHH &*, -H ,H! +H! *H )H!H! (HHH 'H! #$&()639G6HJ! !m ! ! H(HJMM&'rK4!=EYZ[\]9GHK9$&(*, &*, /HHH .H!V l!ۖ69&*! !:MݻM͔N*L&K4!=EYZ[\]9GHK9$ &( *, $&(*,!FH&. *!!@ V!l~!̃",2=?@"Mmop~**!9 BO!( (695!MW<WWlWMc59GHK9$ &( *, Ha*$ &( *, H%FH&O!FH&N*7 &!"*7!8 AN P!b {! !( ( (  (2 :(;A I(i r (!*!  !# .!< H!T*UV*f! !&!7McMMSMUfMTy& * $ &( *, * (FH)a!FH&N* L& K4!=EYZ[\]9GH" *#!$ -:!g k!n t!z ! ! ! ؽ*! !9:&\]^*}!5#gԼM9\}MM%] o5F=$ &( *, *0Le!FH&M<f2!N*2),303!56*T!5*23DH),sף05TMͪ˻;*DH3G$ &( *,o5F=N$ &( *,[x=][x=l&*<!= S!m v!} !/ F!a}       '()+"EF"'(KMN"^#)/12"Q"",[ ] ^ "i    ". ! !% B H I X b c s } ~              " N P "^ <MMa(J.Z  M% M Ҫ  H+$ &( *,"HO"H$ &( *,FH&OOW F UNLCMO"c   ""ACD"W"-gm! ! ?EF ]gh w"",!= T!! ![uw! !! !;=!M a!}L @M -M[w=}, 3GHf$ &( *,OU$ &( *,$ &(*,"FH&"HOW F "H t3uv*:|  (  Ξuޥ c t aM GHGH-GH,M x!GH-N$ &( *,[x=3GH3*12Jܐ( 3*6ܘ 1ؐc5  N =$ &( *,aGH,GH-M hx!GH-N$ &( *, 3*!ڔ !tuTV}~69׃rS}|9GHK9$&(*,M J *H.M  LN=N$ &( *, &(!9 O!ܙ*! ! !* G! !*!696(MMM6K9$&(*,$&(*,*N*L&K4!=EYZ[\]9GH&!N p!t!0236=9acd&q!r v!wx&!Msʅ=y2acqMwƓM01ݙ#"K4!=EYZ[\]9GHK9!$&(*,$&(*,b f L&  6 9!&!wx&!MiMM)MMwM&&L&%K4!=EYZ[\]9GHK9$$&(*,$&(*,!&/!56!WX!mـ!!!69M/mM9GHK9($&(*,!!H.M6Tr! H%!H%L&'$&(*, &*!',0&,L0anp*Mh&hLiaiqnop$&(*,"$&(*,!60 g x$&(*,!L&)K4!=EYZ[\]9GHI6 9$&!l r!s !6 G!!!!& !~ !  np #qst !2!t!!|!!!!!OQ!RSU]r! $&MM MWmWWt2RWh  WfUOL+$&(*,$K4!=EYZ[\]9GHK9*$&(*,#9%;f!&! '!jy!!!!()(* D(qڀ QST6^9kfM)cSkQR`9GHK-$&(*,'$&(*,&(FH)HaL,f$&(*,% ! !69 57;Z\p!bb 5ZFH/@A!FH/K.$ &(!*,)$&(*,(K4!=EYZ[\]9GHV >Qzpuixֵ֒Q^֠ V]O T ֱ ! / ' 5 z ֈ ? A L d  " % ' ( J R   )/֯QpiыѭQєVO Ѩ ! ' { L J Ѹ )ѤѰz GH0$ &(!*,- FH/$ &(!*,,$ &(!*,+FH/@A$ &(!*,*!FH/O$ŞŹ~Չ0>|ŇUk!1Ŕ%4=!T `   Ō , @  œ ! Ŷ **0bgţ Ag;S2EŦŐ ёѪѺ1|U!ч%ѨU  , ъ є *bэA;2іх0T $ &(!*,2$ &(!*,1$ &(!*,0!FH&$ &(!*,/FH&@A$ &(!*,.FH/Q& !5Frŀtœũ%0śߜ$)-?IZn!owſ  1 = ` i L W w ń ū jŐfōS`Xdj(-Ų%5rtђ%ё?ZѵoѴ 1 Ѷ ` L w ўjfSd(ѥ%ΐڳ $ &(!*,7$ &(!*,6$ &(!*,5FH&FH1$ &(!*,4@A$ &(!*,3FH/ 1r{9FŚůov6 9!#s9ȋȩo!#rۭGHK4!=EYZ[\]9GHK/$"&(#*,9$ &(!*,8@AFH/L%efhkmprĖӗęךӜğӡĤӧ !"$/1:<JLTVabfnp{}ĈӊbhmrsΖΜΡΦΧ$<Vf}@STHIH!H,,,,b  0  2!GH2 GHb  0  2!GH< 467OV]^_`tvwx֝.01IPWXYZqstu|֚J PQR7S`RwTRRRRR1SZRtTRRR6_vܟ߽0Ys,,,,,,, , , , , ,,,,H!H!H!3 467Z\]fhiqstu|Ԛ!")+,689BDE[]^suRR7R]RiRtTRRRRR"R,R9RER^Ru6\hsҜ׿!+8D]u,#,",!, ,,,,,,,,,,,,:FkDW>V3C:{Z<P1 I  T t  % f  A Y  a y Pay #<S ".HH>=/8XXHHH @  Title.product'.0$HHRelease.Info.Tab>'A   P P HHHpage Command>=/8XXHHHTitle @ caption.fig list.num/-X Release.Info  Release.info/TXCaveat @ Toc1/.X caption.fig  Command.input/hX Contents.head @ Toc23 Toc.Section  Command.field3(Toc13^(Toc23 sectionhead manual3hhhead13.HHbodyText @% bodytext bold3hhHEAD23: (Toc33 (Toc43x(header &FileSpec3  % OddFooter @rule3  % EvenFooter @% Keystroke3.HH8 %command @ caution.head3/P(a8 %List.Num  footertext 3 headertext3. U % Cover.BarHigh @ Toc.Section3. %caption 3headertext underline @*12point3. %rule release.info.tab @%UCF Closed Title @% product name BodyText2JO  0 caution.head @% Feature Title2.HH0 BodyText2 @% Command Name2NOE  @0 caution.text @% Field Choice6.HH  hardware list @ 'head16( list.num.subpar Diskette List Head6P( Diskette List Head  caution.text6xx Directory List6x Diskette directory head @(head2  Library List6.  caption.tab Diskette directory head @ table.head  table.text @ caption.tab $ sectionnumber @  sectionhead7HH(@Glossary.BodyText @ underline Caveat @  contents.head @ Toc3 @ Toc45n@@@@@@@ @ @ @ @ @@@@@@@@@@@@@@@@@@@ @!@"@Helvetica NarrowNew Century Schoolbook HelveticaITC Zapf Dingbats Helvetica%Times1ITC Zapf Dingbats1 Helvetica Helvetica HelveticaITC Zapf Dingbats Helvetica Helvetica-TimesTimes HelveticaTimesTimesTimes Helvetica,New Century SchoolbookNew Century Schoolbook Helvetica) Helvetica! Helvetica Helvetica Courier Courier CourierITC Zapf DingbatsITC Avant Garde Gothic HelveticaITC Zapf DingbatsITC Zapf Dingbats Helvetica Helvetica9mwmmm7mjEs77Fmm,BBMs7B77mmmmmmmmmm77sssmx7bmxx777\m,mmbmm7mm,,b,mmmmBb7mbbbbB3BsBB7mjm777WBmmmxmbmmmxmBBxBB&BBBm\\\\yocyyddo8nydnnyyynnn8;Noo)CCdy8C88oooooooooo88yyyYQo~zCyCyd)ooYsdCkz?;w?zdsoY]Nzkkk`CyCyCC8dyd888BCooddzYdddsoC;YNN)N44oyyyMMMMyocyyooo8nyonnoFunnn8C_oo8CCNu8C88ooooooooooCCuuuzz8ozzzC8Cuo8ozozoCzz88o8zzzzNoCzooodN8NuCC8ooo888HCoozzzoooozoCCzdd0dCCoyyyMMMMydcyyddd2nydnn[Fqnnn2nrcnksX7SNNCC2dko888mmw}\]MNbN]N]]mN]NN]]N]N]N]NNNm]mNm]]NNNNe]]]C]]llll,-,,ddMddot! !! 777 z!77! !!!! oooM!Xd``ddd!!77!!++o,-,,dd <<<xVlulz.R10100.:;;<=>FI<PIMFLq*!,<=63=0JF<<:;<:<]01100ee;:7o  doooVV!%l 006;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;fO+r+osssN]KrrottaNN[[^^0z4Z4ccL]somdYvmmddd2cmdcca?iccc22@ddx(<<Fi2<22dddddddddd22iiidxxxn2Zxdxxnxxxn222Td(ddZdd2dd((Z(dddd<Z2dZZZZ</<i<<2dad222A<xdxddndZdddnd<<n<<"<<<dmmmEEEE`YxOi``YYY,X`YXXV8]XXX,,9YYk$55>],5,,YYYYYYYYYY,,]]]Ykkttkb|t,PkYt|k|tkbtkkkb,,,KY$YYPYY,YY$$P$YYYY5P,YPtPPP5*5]55,YVY,,,:5kYkY|Y|btYPYYYbY5vv5b55555Y```====`YxOi``YYY,X`YXXY8]XXX,5LYYt,55>],5,,YYYYYYYYYY55]]]bttttkb|t,Ytbt|k|tkbtkkkb5,5]Y,YbYbY5bb,,Y,bbbb>Y5bY|YYP>->]55,YYY,,,:5tYtY|b|btbYYYYbY5vv5bPP&P55Y```====`xPxOxi``PxPP(X`PXXH8ZXXX(s~~nXyzz[lzzyyOXV\o~~~~~wtx~o|{yqqmp~~qnon~~r~zzzyy~}F,B??kk55(PVY,,,tuWWkzz|_od~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~IxxJoo=z{{TuNiEu\TTNuNN'MTNMMK1RMMM''2NN|]//6R'/''NNNNNNNNNN''RRRN]]ee]Vme'F]Nuem]me]Ve]]]V'''BNNNFNN'NNFuNNNN/F'NFeFFF/$/R//'NKN'''3/]N]NmNmVeNFNNN|VN/gg/V/////NTTT6666,,ccc,cd~dx@dxxdxddxx_d,Txdxdxddd@xexxdhhdddxh@x  hxVxxhhhydcyyddd2nydnn[Fqnnn2CRddCCCdq2C28dddddddddd88qqqYzoCNzoozzC8C^dCYdYdYCdd88d8ddddCN8ddddY`(`lCC2d[d222BCYYdddYYYYddCCYYY$YCCdyyyMMMMydcyyddd2nydnnlFrnnn2CoddCCCdr2C28ddddddddddCCrrrdzNdzoC8CtdCdoYoYCdo8Co8odooYNCodddYO,OhCC2dld222BCddddoYYYYodCCddd8dCCdyyyMMMMmdYvmmddd2cmdccd?iccc2<Udd2<<Fi2<22dddddddddd<<iiinxn2dnxxnxxxn<2<id2dndnd<nn22d2nnnnFd<ndddZF2Fi<<2ddd222A<ddnnnddddnd<<nZZ+Z<<dmmmEEEEmZYvmmZZZ-cmZccR?fccc-<IZZ<<<Zf-<-2ZZZZZZZZZZ22fffPxxnd<Fndxdnn<2<TZ<PZPZP<ZZ22Z2ZZZZ<F2ZZZZPV$Va<<-ZRZ---;<PPZZZPPPPxZZ<<PPP P<<ZmmmEEEE`xPxOxi``PxPP(X`PXXH8ZXXX(5APP|555PZ(5(,PPPPPPPPPP,,ZZZGtkktbYtt5>tbttYtkYbttttb5,5KP5GPGPG5PP,,P,|PPPP5>,PPtPPGM MW55(PHPZZ(((55tGtGtPtPtPGGGGkPP5zz5GGGG55P```====xwxxx<xmT<PbxxPPPx<P<CxxxxxxxxxxCCkP]PCPqxPkxkxkPxxCCxCxxxxP]Cxxxxks0sPP<xmx<<<OPkkxxxkkkkxxPPkkk+kPPx\\\\,,ccc,cd~dd@Pxxdxddddmd,TdddPdPPP,xdx^xxxdhhdddxh@x  hxxxExxxhhhyscyyddd9nydnnyynnn9;Css0NNdy8C88s]ssssssss88yyydYNyNyd0zosNzJFFzhdUzzzkNyNyCC9dd999BCzzzzossszsC;d``0`CCdyyyMMMMyocyyddd8nydnnyynnn8CPyo)CCdy8C8yoooooooooo88yyyYQzCyCyd)soYzYCkzC?oCzdsoYYFzhdd]CyCyCC8dd888BCssddzYYYYooCCYNN8NCCdyyyMMMM  <<< <YpYkYkk|YkYYkk8Y .kYkYkYYY|k|Z|kkY@@YYYtk@k@kLkk@@@{{{{wCTCPrCPP]CPCCPPCPCPCPCCC]Px]C]PPCCCCWPPPxx9xPP\\\\mdYvmmddd2cmdcca?iccc22@ddx(<<Fi2<22dddddddddd22iiidxxxn2Zxdxxnxxxn222Td(ddZdd2dd((Z(dddd<Z2dZZZZ</<i<<2dad222A<xdxddndZdddnd<<n<<"<<<dmmmEEEEwCTCPrCPP]CPCCPPCPCPCPCCC]Px]C]PPCCCCWPPPxx9xPP\\\\ydcyyddd2nydnn[Fqnnn2nrcnksX7SNNCC2dko888mmw}\]Mypcyyppd8nypnnxxxnnn88Hxp8LLXx8T8\pppppppppp88xxxpth`8`|XpthT|d@@xd88x04t0x@X<xppt\DxDxTT8dxp888HTxxpH8p``,`00dyyyMMMM<S8K1SccB<<c8S8c87<8776#:777$88YC!!':!8888888888:::8fCCHHC=NH2C8SHNCNHC=HC^CC=/888288882S8888!282H222!!:!!868dd$!C8C8N8N=H82888dY=8!JJd!=!!!!!8ddd<<<&&&&ydcyyddd2nydnn[Fqnnn2nrcnksX7SNNCC2dko888mmw}\]M`xPxOxi``PxPP(X`PXXH8ZXXX(s~~nXyzz[lzzyyOXV\o~~~~~wtx~o|{yqqmp~~qnon~~r~zzzyy~}F,B??kk55(PVY,,,tuWWkzz|_od~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~IxxJoo=z{{yocyyooo8nyonnkFunnn88Goo,CCNu8C88oooooooooo88uuuoz8dozz888^o,oodoo8oo,,d,ooooCd8oddddC4CuCC8oko888HCooozodooozoCCzCC&CCCoyyyMMMM! i<!!   !    [          %[[[[@%u[ [%[u@u[@%[@@@%  % % %% %%%% % u     [ [ u%u%[%    % bb%r !!!GL?308$+OBJECT1[tt)))??;3;5?TBGۼDG y1ᮧ1==77=p=py 1ᮧlswsw& & 7,1,1ᮧ p77tytp ZZ|ZJhJhZ ho|oCaCZJhJh [d!;d$c:b^9baLJ`[`d_Ȉ1_0^&^(]B]L\\.\.[썲[[\b[P[ӐG[G[SV[ u[͓[[?\Q\\?]y]q]l^^ x_ `ꚤ`DCaaϛb5c.cJdUdUeU=f;fg>hhg{ijjB&kЙkO&lØl,lNmmImnQn tndnn摇n,{nndn;nm:mzmڌ"m;lalkmpkjiWji&i:hgEgrfGe*Fe$d! tltút 0Nk0=s2DWh80NkGL         ?            ?   @@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@?@???????????????     p ,    `   k 5  \   U  XU ?             ?     p  W  `U  VU  `UU  TUU   UUU x \UUU  5UUUU  VXUUUU : PUUUUU પ @UXUUUUU  WUUUUUUU  XUupUUUUUU  `UU WUUUUUU z UUpUUUUUUUTUU5VUUUUUUUꫪPUUUUUUUUUU5પUUUUUUUUUU VUUUUUUUUUXUUUUUUUUU * @UUUUUUUU  UUUUUUUU  \UUUUUU j `UUUUUU5  UUUUUU  VUUUUU  PUUUUU * @UUUU  WUUU  XUU j `UU5  UU  TU  pU *    પUUUUUUUUUU VUUUUUUUUUXUUUUUUUUU * @UUUUUUUU  UUUUUUUU  \UUUUGL 659.91 336245 000000000102 M 02-03 12-59 00 27 0279 812501 323545 75 00000690570068 KT V 00000000 872.95 336245 000000000102 M 02-03 13-00 00 27 0284 812501 323545- ""?      b n Picture 10B0$0b00 S_2XXXPBPSRR@(-mr5mr5VVVV;o;oV +V +m-mR@,r5mb(KodKod4I4;oVVVr5Vr5mR@t +W];oW];oK-K +W]RR@xUgP0y00y0UgUgR@|0Ug]P]++0y00y0UgPSR@lgXXkX*XAtX]XXXY/=YtYzZ!ZuZ[:E[ \\]]t]g^za^a_vl_`o`aba#bKebcc}Ecd@ dqdeLeXe2ee,ef,f gf f ceedeeReoe80dddc\dccOLbbba#a%I`c`*m_z_/q^h^7W]9]C \\Q[l[t*[ZZD/YYbYPY XXXt#XNX2$XXgXPSRR@p^ndnn^nRR@x9E9'"g8O$9E @00000690610302 KT H 00000000 200.00 323545 000000020000 O 02-03 16-36 55 14 3263 289590 323545 70 00000690610302 KT H 00000000 385.00 323545 000000031000 O 02-03 16-25 55 17 2793 819352 323545.T 70 00000690640317 KT H 00000000 5,800.00 336245 000000000000 O 999 02-03 15-15 55 13 2486 034010 323545 70 00000690650037 KT H 00000169 4,018.33 323545 000000371833 G 02-03 12-09P00033>CADObj-$$08:00:11.tmp Q3`EO$000 p*rp*rp*r*X#*gDHUU2hltlt 4hMC!t!(3F(0(30tcccz3!! E G!(հ}Y$B=3.0G!! r V ! J)1>J+O1QSWXZcf jy>c`