ADAOPR

March 28, 2018 | Author: Ulises Samaniego | Category: Kernel (Operating System), Parameter (Computer Programming), Databases, Thread (Computing), Operating System
Share
Report this link


Comments



Description

1ADAOPR (Operator Utility) This document describes the utility "ADAOPR". The following topics are covered: Functional Overview: This describes the utility and provides information concerning the use of operating system resources. • Procedure Flow: This provides a graphical representation of the interaction between database components while the utility is running. Also, a list of the operating system environment variables used by the utility is provided. • Checkpoints: This describes the checkpoints written by the utility. • Control Parameters: This describes the parameters which are available for the utility. • Functional Overview The DBA uses this utility to operate the Adabas nucleus. This utility is a multi-function utility. Procedure Flow Data Set Control statements ADAOPR messages Environment Variable stdin stdout Storage Medium Additional Information Utilities Manual Messages and Codes The following control parameters are available: ABORT BFIO_PARALLEL_LIMIT = number CANCEL CLEAR_FILE_STATS = (number [- number] [, number [- number] ] ... ) CSA = string DBID = number DISPLAY = (keyword [,keyword]...) ES_ID = number 2 D [NO]ET_SYNC EXT_BACKUP = [PREPARE | CONTINUE | ABORT] FEOF = (keyword [,keyword]) FILE = number ID = number ISN = ( number [- number] [,number [- number] ] ... ) [UN]LOCK = (number [,number]...) LOGGING = (keyword [,keyword]...) LOGIN_ID = number MGC = number NISNHQ = number NODE_ID = string OPTIONS = (keyword [,keyword]...) RESET = keyword D [NO]RESPONSE_ABORT RESPONSE_CHECK = (number[-number][,number[-number]]...) SET_FILE_STATS = (number[-number][,number[-number]]...) SHUTDOWN STATUS = (keyword [,keyword]...) STOP = (number[-number][,number[-number]]...) TNAA = number TNAE = number TNAX = number TT = number USER_ID = string WRITE_LIMIT = [number] XA_RESPONSE_CHECK = (keyword [,keyword]...) All command processing is immediately stopped. A large buffer flush. In this case. A BT command is issued for each active ET user and the session is terminated. If a value of 0 is specified. The maximum value for ´number´ is defined by the Adabas system.number] ] . slowing down command throughput and possibly causing applications to stall if a buffer flush is active. CANCEL CANCEL This function terminates the Adabas session immediately. the buffer flush sets up the specified number of I/Os and waits until these have been processed before issuing the next packet. allowing earlier processing of concurrent I/Os from other threads. The name of the SMP dump file is SMPPOS. display functions are still possible with ADAOPR but parameter modification commands are no longer permitted.number] [..hh:mm:ss (UNIX platforms only). The communication link to the database is cut but the shared memory is still held. for example. BFIO_PARALLEL_LIMIT BFIO_PARALLEL_LIMIT = number This function sets the number of parallel I/O requests by a buffer flush. can cause the I/O queue to be very busy. The session is terminated abnormally with a pending AUTORESTART. CLEAR_FILE_STATS CLEAR_FILE_STATS = (number [. number [. and other I/Os (such as buffer pool read I/Os and WORK I/Os) can be enqueued for a long time.3 Checkpoints The following table shows the nucleus requirements for each function and the checkpoint written: Function FEOF=PLOG Nucleus must be active Nucleus must NOT be active Nucleus is NOT required Checkpoint written SYNC Control Parameters ABORT ABORT This function terminates the Adabas session immediately. ABORT causes the SMP dump file to be written to the databases's default directory.APP. If BFIO_PARALLEL_LIMIT is specified. ) . the number of buffer flush I/Os is unlimited.. a so-called database section file.005. Multiple DBIDs are supported within one session. For example. if the database ID is 5. Example: adaopr: adaopr: adaopr: adaopr: adaopr: dbid=1 shutdown dbid=2 shutdown dbid=3 . and the file creation was initiated by a trapped response code 113. Adabas. If a file with the same name already exists in this directory.RSPyyy.hh:mm:ss Adabas. the file name will start with Adabas. DBID DBID = number This parameter selects the database to which all subsequent ADAOPR commands apply. `yyy' is the trapped three digit response code. if the database ID is 5. The following naming conventions are used for the file: Adabas.hhmmss (with the NORESPONSE_ABORT option set).g. `hh:mm:ss' is the time the file was created. e. For example. Adabas. the file name will start with Adabas. CSA CSA = string `string' is a file specification of a file containing status information from an Adabas nucleus. The DBID and CSA parameters are mutually exclusive. This file may be created by an ADAOPR ABORT function.xxx.4 This function disables the collection of I/O statistics enabled by SET_FILE_STATS for the specified file(s).g. by an abnormal termination of Adabas.hhmmss Adabas. The default is the directory from which the nucleus was started. and then the time of creating will be appended. and then the time of creating will be appended. where • • • • `xxx' is the three digit database ID.xxx.005.121650.RSPyyy. `hhmmss' is the time the file was created.12:16:50.xxx. The file will be created in the directory that is pointed to by the environment variable ADA_CSA_DUMP. or by response check trapping (refer to the RESPONSE_CHECK function for further information).RSP113.005. The DBID and CSA parameters are mutually exclusive. and the file creation was initiated by a trapped response code 113. it will be overwritten.RSP113.xxx.hh:mm:ss Adabas.RSP113. e.005.RSP113. Command table display. Protection log statistics.. User time limits display.adaopr: shutdown adaopr: quit 5 DISPLAY DISPLAY = (keyword [. Static nucleus parameters display.keyword]. High water marks display. Command queue display. The corresponding values are always truncated. Internal command queue display.) This parameter displays various information during an Adabas session. Buffer pool statistics display. User queue display. File I/O display. Meaning The following examples show the information produced by the various keywords.. An undefined value (divided by 0) is specified with " *%" and an overflow with "***%". together with explanations of the information that is displayed. The following keywords can be used: Keyword ACTIVITY BP_STATISTICS COMMANDS CQ DYNAMIC_PARAMETERS FILE_IO FP_STATISTICS HIGH_WATER HQ ICQ PLOG_STATISTICS STATIC_PARAMETERS TT UCB UQ UQ_FILES UQ_FULL UQ_TIME_LIMITS Database activities display. Utility communication block. Thread table display. Example: DISPLAY=ACTIVITY adaopr: display=activity ADANUC Version <version number> . Full information about user queue element. Some of the following displays include percentages. User file list display. Hold queue display. Format pool statistics display. Dynamic nucleus parameters display. EXAMPLE: DISPLAY=BP_STATISTICS adaopr: display=bp_statistics Database 76 Buffer Pool Size : ADANUC Version <version number> Buffer Pool Statistics on 19-JUL-2005 14:58:10 6. o the number of commands waiting because ISNs are held by another user.physical read I/Os) * 100) the format pool hit rate. o read and write I/Os for WORK and PLOG. o the number of commands thrown back because of dynamic work pool overflow. INTERRUPTS shows the current and total number of workpool space waits.110.456 RABNs present ------------ASSO DATA WORK Pool Allocation --------------Current ( 81%) : Highwater ( 81%) : 5. o the number of commands waiting for ET synchronization.440 728 647 194 Total ----99% 98% on 28-JUL-2005 13:19:30 Throwbacks ---------Waiting for UQ context Waiting for ISN ET Sync DWP Overflow Interrupts ---------WP Space Wait Current ------0 Total ----87 53 0 0 Total ----0 6 The information has the following meaning: • • • I/O ACTIVITY shows the total numbers of: o physical buffer pool I/Os (physical read I/Os + physical write I/Os). The buffer pool hit rate is calculated using the following formula: o hit rate (in %) = / logical read I/Os ((logical read I/Os . The format pool hit rate is calculated using the following formula: o hit rate (in %) = ((translated FBs * 100) / required FBs) • THROWBACKS shows: o the number of commands waiting for session context because internal commands were running.108. This is the relationship between the logical read I/Os and the physical read I/Os.291. This is the relationship between the number of format buffer requests (required FBs) and the required format buffers already translated in the format pool (translated FBs). POOL HIT RATE shows: o the buffer pool hit rate.Database 76 I/O Activity -----------Buffer Pool WORK Read WORK Write PLOG Write Pool Hit Rate ------------Buffer Pool Format pool Activity Total ----5.736 5.784 : : : 1.426 265 207 . o the size in bytes and percentage of the buffer pool high water mark (see also the display for DISPLAY=HIGH_WATER).216 ( 10%): ( 8%): The information is interpreted as follows: • • • • POOL ALLOCATION shows: o the size in bytes and percentage of the buffer pool that is currently in use.100 521. If the modified bytes in the buffer pool reach this limit.884 0 7 L2 L3 L4 L5 L6 L9 LF MC N1 N2 553 1.124 569 420 436 456 20 0 877 0 OP RC RE RI S1 S2 S4 S8 S9 25 89 0 0 1. o the size in bytes and percentage of the currently modified bytes in the buffer pool.I/O Statistics -------------Logical Reads Physical Reads Pool Hit Rate Physical Writes : : : : 251. o the total number of buffer flushes that were made in order to get free space. o the buffer pool hit rate (please refer to the example for DISPLAY=ACTIVITY for the buffer pool hit-rate formula). an automatic buffer flush is started. o the total number of physical buffer pool write I/Os. I/O STATISTICS shows: o the total number of logical and physical buffer pool read I/Os (both numbers are required in order to calculate the buffer pool hit rate).511 81 12 230 50 .006 72 0 643 ADANUC Version <version number> Commands on 19-JUL-2005 14:58:10 9. DATA and WORK RABNs currently in the buffer pool.090 Buffer Flushes -------------Total To Free Space Write Limit Modified 7 : : 32 0 629. RABNs PRESENT shows: o the number of ASSO. Example: DISPLAY=COMMANDS adaopr: display=commands Database 76 ADABAS Commands: A1 req-count Rda req-count A1 BT C1 C3 C5 CL E1 ET HI L1 892 736 40 0 10 32 1.186 350 99% 5. o the size in bytes and percentage of the buffer pool write limit. The buffer pool write limit is automatically adjusted if not explicitly set in ADANUC or ADAOPR. BUFFER FLUSHES shows: o the total number of buffer flushes. LOGIN ID shows the login user identification string. the value displayed is the number of MC calls plus the number of single Adabas commands contained in the MC calls. Updates made by utilities are not included in the display. Example: DISPLAY=CQ adaopr: display=cq Database 76 No -1 2 3 4 5 6 7 8 9 10 11 Node Id ------ADANUC Version <version number> Command Queue on 19-JUL-2005 14:58:10 ES Id ----21243798 21231788 21230756 21227398 21247630 21246388 21219466 21237160 21246610 21246896 21244730 Cmd File --. the process ID). Used: 11. CMD shows the command string. The local node is represented by an empty string. ES ID shows the environment-specific identification (for example. For MC commands. FILE shows the file number. The final line of the display shows how many command queue entries were selected according to the currently active selection criteria. .8 This command displays the total numbers of Adabas commands issued in the current session. and how many entries are used in total in the command queue. Queue Size: 20 This display shows the current command-queue entries: • • • • • • NODE ID shows the node identification string. STATUS shows the status of the command-queue entry. A read command that is issued while the multifetch option is set is counted as a single command.---E1 12 E1 12 L2 12 S1 12 S1 12 A1 12 S1 11 L6 11 A1 11 S1 11 U0 0 Status ----Ready to Running Ready to Running Running Ready to Ready to Ready to Running Running Running Login Id -------miller jones smith miller smith jones jones smith miller miller dba run run run run run Selected: 11. during a utility run). Waiting for user queue entry.243. Complex command is waiting to run. No entry in thread table.160. The required entry is locked by an active internal command. Placed in queue and ready for scheduling. Waiting for ISN in file shown in column "File" in the display. Running in a thread (see DISPLAY=TT). user is no longer active. Example: DISPLAY=DYNAMIC_PARAMETERS adaopr: display=dynamic_parameters Database 76 Resources: Time Slices: Group Commit: Logging: ADANUC Version <version number> Dynamic Parameters on 19-JUL-2005 14:58:10 NISNHQ TNAA TNAE MGC CLOG : : : : : OFF : 84.9 The possible status values are shown in the following table: Status Completed Marked For Deletion New Ready To Run Running Waiting For Complex Waiting For Et Sync Waiting For Isn <isn> Waiting For Space Waiting For Uqe Command processing completion. Waiting for working space.164-182. Command is marked for delete. which are only used internally by Adabas (for example. Meaning Waiting For Group Commit Waiting for group ET. No entry in thread table. The "RUNNING" and "COMPLETED" values may differ even if the user has not specified an explicit selection criterion. Waiting for ET synchronization. Command is ready to be inserted in the scheduling queue. Example: DISPLAY=FILE_IO adaopr: display=file_io .251-252 100 900 900 50 WRITE_LIMIT: TNAX TT : : 900 300 Response check with ABORT This display shows the current values of the dynamic nucleus parameters. Note: The display may show command codes such as "U0". No entry in thread table. .547 98% 0 0 162 1 Global -----3 2 66% 0 0 This display shows the format pool statistics: • • POOL ALLOCATION shows: o the size in bytes and percentage of the local and global format pools that are currently in use.000 84 84 Local ----11. o the total number of valid format buffers that are overwritten in the format pool (replacements). The I/Os are only counted if the ADAOPR function SET_FILE_STATS is activated. POOL STATISTICS shows: o the total number of scans and hits of valid format buffers in the format pool (both numbers are required in order to calculate the format pool hit rate).869 2. The formula for the hit rate value is given in the description of DISPLAY=ACTIVITY. o the format pool hit rate (please refer to the example DISPLAY=ACTIVITY for the format pool hit-rate formula). their hit rate and the writes the buffer pool manager has made for every file since database was started.149 This display shows the logical and physical reads.656 251.070 Physical -------180 148 Hit Rate ---99% 99% Writes -----2. Example: DISPLAY=FP_STATISTICS adaopr: display=fp_statistics Database 76 ADANUC Version <version number> Format Pool Statistics on 19-JUL-2005 14:58:10 251.10 Database 76 ADANUC Version <version number> File I/O on 19-JUL-2005 14:58:10 Reads File ---11 12 Logical ------145.341 99.656 Pool Contents ------------Local Format Buffers: Global Format Buffers: Maximum Local Pool Size: Maximum Global Pool Size: Pool Allocation --------------Local Current ( 22%) : Local Highwater ( 27%) : Global Current ( Global Highwater ( Pool Statistics --------------Scans Hits Hit Rate Replacements Overflows 0%) : 0%) : 57.540 70. o the size in bytes and percentage of the local and global format pool high water marks.780 11. the value in this column can be larger than 100 %. If the high water mark exceeds the size. If a transaction's protection information spans more space than allowed by "Active Area". LWP (workpool).584 1. LAB (attached buffer). NCL (client queue).136 146 1 158 % 14 55 100 5 83 100 39 97 13 68 25 Date/Time --------19-JUL-2005 10:50:48 19-JUL-2005 10:50:54 19-JUL-2005 10:46:04 19-JUL-2005 10:46:13 19-JUL-2005 10:47:26 19-JUL-2005 10:45:54 19-JUL-2005 10:46:04 19-JUL-2005 10:51:58 19-JUL-2005 10:45:54 19-JUL-2005 10:52:17 19-JUL-2005 10:52:08 48 19-JUL-2005 10:50:58 2 19-JUL-2005 10:45:46 52 19-JUL-2005 10:50:28 This display shows the high water marks for the current session: SIZE shows the size in bytes of pools and buffers. For queues. threads and hold queue user limit. complex search). • The entries in the column AREA/ENTRY correspond to the ADANUC parameters NU (user queue). NH (hold queue).000 50.000 98.584 1. it shows the number of entries. o Example: DISPLAY=HIGH_WATER adaopr db=076 display=high_water Database 76 Area/Entry ---------User Queue Command Queue Hold Queue Client Queue HQ User Limit Threads Workpool ISN Sort Complex Search Attached Buffer Buffer Pool Protection Area Active Area Group Commit Transaction Time ADANUC Version <Version number> High Water Marks on 19-JUL-2005 10:52:08 Size ---100 20 100 50 100 6 170.627. • DATE/TIME shows the date/time at which the high water mark occurred. TT (transaction time). • IN USE shows the size in bytes or number of entries currently in use. it receives a response 9 (LP). this can occur if the value is decreased by ADAOPR.627. o the number of valid global format buffers in the format pool. NT (threads). POOL CONTENTS shows: o the number of valid local format buffers in the format pool. NC (command queue).11 • Overflows. LP (protection area).660 67. resulting each time in a response 42. For example.456 1.136 0 High Water ---------14 11 100 5 83 6 67.896 6. NISNHQ (hold queue user limit). The entry "ACTIVE AREA" is the largest part of WORK part 1 that can be used by a single transaction. the nucleus displays a PLOVFL message and a value of more than 100 in the "%" column of the highwater display. • % shows the relationship between the high water mark and the size.000 300 50 300 In Use -----14 11 100 1 6 0 67.304 6. • HIGH WATER shows the maximum quantity required simultaneously for the given area/entry.232 48. MGC (group commit). . LBP (buffer pool). This is the number of times that a format buffer exceeded the format pool size. LS (ISN sort.000 50.291. Users who have set user-specific timeout values in their OP call are not included in the values for Transaction Time. There is no output in this column if the high water mark is 0. 222 X 2 X Flg --M Selected: 8. • An M for FLG indicates that the record has been modified. Adabas utilities use the utility name preceded by an asterisk as the USER ID. and how many entries are used in total. • ISN shows the number of the ISN in hold. NODE ID shows the node identification string. display=hq Database 76 Id Node Id -. In Adabas Version 5.12 Note: 1. Queue Size: 101 This display shows the internal command queue: . 2. if the ADAOPR parameter CSA is used. The local node is represented by an empty string. LOGIN ID shows the login user identification string. Queue Size: 160 This display shows the current hold-queue entries: ID shows the internal user identification of the user holding the ISN. USER ID shows the user identification.----2. Values for Attached Buffer and Command Queue are not displayed correctly if the nucleus cannot be contacted by ADAOPR (for example. • • • • • The final line of the display shows how many hold queue entries were selected according to the currently active selection criteria. Entries are displayed in unsorted sequence.------15 19 ADANUC Version <version number> Hold Queue on 19-JUL-2005 14:58:10 Login Id -------miller smith ES Id ----6974 7056 User Id ------*adatst *adatst File ---11 11 ISN Locks --. process ID).1 only X = exclusive lock is supported. ES ID shows the environment-specific identification (for example. Example: DISPLAY=ICQ adaopr: display=icq Database 76 Id -16 Node Id ------ADANUC Version <version number> Internal Command Queue on 19-JUL-2005 14:58:10 Login Id -------smith ES Id ----21246610 Command ------STOP Status -----Ready to run Selected: 1. Therefore. Used: 2. the high water mark for threads will be the same as the value shown in the Size column in most cases. Used: 1. • LOCKS shows the kind of lock for the ISN. Example: DISPLAY=HQ adaopr: file=11. Threads are used in a round-robin manner. • FILE shows the number of the Adabas file in which the ISN is located. WAITING FOR ET SYNC or WAITING FOR UQE.683 KB 32 KB 115.291.456 170. BI ADANUC Version <version number> Static Parameters on 19-JUL-2005 14:58:10 : : : 98. and how many entries are used in total.304 6. RUNNING.13 Command AR BT BTCL CANCEL DELUQE ETSYNC SHUT STOP TIMEOUT Autorestart Back out transaction Back out open transaction and close user Cancel nucleus Release file list and delete user queue element Start an ET-SYNC status check after a global transaction has received a timeout Shut down nucleus STOP from ADAOPR Non-activity timeout Meaning The status of internal commands can be READY TO RUN.000 NT NU NCL : : : 6 100 50 Logging: . Example: DISPLAY=PLOG_STATISTICS adaopr: display=plog_statistics Database 76 Active PLOG ----------Session Number Extent Active Since Duration ADANUC Version <version number> PLOG Statistics on 19-JUL-2005 14:59:41 : : : : 37 2 19-JUL-2005 14:59:41 00:00:01 24.200 KB/h Allocated Space : Used Space ( 0%) : Average Growth Rate : Example: DISPLAY=STATIC_PARAMETERS adaopr: display=static_parameters Database 76 Resources: LAB LBP LWP PLOG. The final line of the display shows how many internal command queue entries were selected according to the currently active selection criteria. 782 1. Simple . active active active active active active This display shows the entries in the thread table. The file number is 0 if the corresponding thread context is not active. • FILE shows the file number of the Adabas command that is currently being processed from the corresponding thread context. • CMD shows the command string of the Adabas command that is currently being processed from the corresponding thread context. There is no output in this column if the corresponding thread context is not active. Update . Simple . The number of displayed entries is simultaneously the high water mark for threads.Options: Userexits: TRUNCATION 4 14 This display shows the static nucleus parameters.475 10. CMD COUNT shows the total number of Adabas commands processed from the corresponding thread context. Complex. or if the command is a global one which is not linked to a particular file.566 21. because internal commands are also counted. Example: DISPLAY=TT adaopr: display=tt Database 76 No -1 2 3 4 5 6 Cmd Count --------10. • STATUS shows the command type and the status of the corresponding thread context.516 3. The sum of these counts will normally differ from the sum shown by DISPLAY=COMMANDS. Update . • Possible command types are: • • • Update Simple Complex .713 File ---0 11 12 12 11 12 ADANUC Version <version number> Thread Table on 19-JUL-2005 14:58:10 Cmd --U0 S1 S1 S1 A1 E1 Status -----Update .382 2. FILE or PLOG.----UTO 13 This display shows the utility communication block.15 Possible entries for the thread status are shown in the following table: Status free ready active waiting for io <rabn>/<block type> waiting for <rabn>/<block type> waiting for space <size> bytes available for allocation ready to run running waiting for i/o completion of block <rabn> waiting for access/update synchronization of block <rabn> waiting for <size> bytes of work pool space Meaning The block type can be ASSO. DATA. UTILITY shows the name of the utility. WORK. Example: DISPLAY=UCB adaopr: display=ucb Database 76 Date/Time --------19-JUL-2005 14:59:41 ADANUC Version <version number> UCB on 19-JUL-2005 14:59:45 Entry Id -------42 Utility ------adaopr Mode Files ---. . MODE shows the mode in which the files are being accessed. • • • • • DATE/TIME shows the date and time on which the given files were locked. The possibilities are: o ACC open for access o UPD open for update o EXU open for exclusive update (parallel access allowed) o UTO open for utilities only o UTI open for exclusive access (no parallel access or update allowed) Files shows the file numbers of the files that are locked. ENTRY ID shows the allocated identification of the entry. LOGIN ID shows the login identification string. TYPE shows the user type: o AC access only user o ET ET user o EX exclusive update user o EX.16 Example: DISPLAY=UQ adaopr: display=uq Database 76 Id -26 23 20 19 18 16 17 14 13 12 11 Node Id ------ADANUC Version <version number> User Queue on 19-JUL-2005 14:58:10 Login Id -------dba smith jones jones smith smith jones miller dba dba dba ES Id ----21244730 21230756 21231788 21219466 21246896 21246610 21246388 21243798 21239674 21239672 21239670 User Id ------*adaopr Type ---UT ET ET ET ET ET ET AC EX. The local node is represented by an empty string. Example: DISPLAY=UQ_FILES adaopr: display=uq_files Database 76 ADANUC Version <version number> User Files on 19-JUL-2005 14:58:10 . NODE ID shows the node identification string. STATUS shows the status of the user: o E user at ET status o G global timeout (XA) o I user session started with an implicit OPEN o P pending ET (XA) o R restricted file list o T user has received a time-out o U user specific timeout interval value The final line of the display shows how many user queue entries were selected according to the currently active selection criteria.ET EX Status -----E I IE T E RU ######## *adatst *adatst DBADMIN R Selected: 11. • • • • • • ID shows the internal user identification. Used: 11. USER ID shows the user identification. and how many entries are used in total.ET exclusive update user with ET logic o UT utility user. Queue Size: 100 This display shows the current user queue entries. TYPE shows the user type (please refer to the DISPLAY=UQ example for more information). MODE shows the mode in which the files are being accessed: o ACC open for access o EXF open for exclusive access (no parallel access or update allowed) o EXU open for exclusive update (parallel access allowed) o UPD open for update o UTI open for exclusive access (no parallel access or update allowed) o UTO open for utilities only • FILES shows the Adabas file list of the user entry.ET EXU EX ACC EXU Files ----11-12 11-12 11-12 11-12 11-12 11-12 14 11 13 Selected: 10.17 Id -26 23 20 19 18 16 14 13 12 11 Type Mode ------UT ET UPD ET UPD ET UPD ET UPD ET UPD ET UPD AC EX. and how many entries are used in total. Example: DISPLAY=UQ_FULL adaopr: file=13.200 0 1 TNA ISNs Held : : 2.400 0 . If the list is too large to be displayed in one line. ID shows the internal user identification. Start : Last Activity : 19-JUN-2005 14:53:07 Time Limits: TT Resources: ISN Lists Open Files : : : 1. Used: 11. Queue Size: 100 This display shows the file lists for active users. • • • The final line of the display shows how many user queue entries were selected according to the currently active selection criteria. display=uq_full Database 76 User Entry: Id Node Id User Id User Type ADANUC Version <version number> Full User Queue Entry on 19-JUL-2005 14:58:10 : : : : 11 DBADMIN EX User Status : RU ES Id Login Id : : 21239670 dba Time Stamps: Session Start : 19-JUL-2005 14:53:07 Trans. several lines will be used: file numbers are not omitted. Activity: Language: ADABAS Calls : User Encoding : 1 1 Transactions : 0 18 This display shows detailed information about user queue elements. Example: DISPLAY=UQ_TIME_LIMITS adaopr: display=uq_time_limits Database 76 TNAA Interval TNAE Interval : : ADANUC Version <version number> User Time Limits on 19-JUL-2005 14:58:10 00:15:00 00:15:00 Timeout Interval ---------------00:15:00 00:05:00 00:15:00 00:05:00 00:15:00 00:05:00 00:15:00 00:05:00 00:15:00 00:05:00 00:15:00 00:05:00 00:15:00 00:15:00 00:05:00 00:15:00 00:05:00 00:15:00 00:15:00 00:05:00 00:40:00 TNAX Interval TT Interval : : 00:15:00 00:05:00 Start Date/Time --------------19-JUL-2005 14:58:10 19-JUL-2005 14:58:10 19-JUL-2005 19-JUL-2005 19-JUL-2005 19-JUL-2005 19-JUL-2005 19-JUL-2005 19-JUL-2005 19-JUL-2005 19-JUL-2005 19-JUL-2005 19-JUL-2005 19-JUL-2005 19-JUL-2005 19-JUL-2005 14:58:10 14:58:10 14:58:10 14:58:10 14:58:10 14:58:10 14:58:00 14:58:10 14:58:10 14:58:10 14:58:10 14:58:10 14:53:11 14:53:11 Id St Limit -. response 9 has not been collected yet by the client. The final line of the display shows how many user queue entries were selected according to the currently active selection criteria. ST shows the status of the entry. LIMIT describes the timeout type. TIMEOUT INTERVAL shows the current active timeout intervals. Queue Size: 100 This display shows the current timeout limits for the user queue entries. and how many entries are used in total.----23 TNAE TT 22 TNAE TT 21 TNAE TT 20 TNAE TT 19 TNAE TT 18 TNAE TT 17 TNAA 16 TNAE TT 14 TNAE TT 13 TNAA 12 TNAE TT 11 U TNAX Remaining Time -------------00:15:00 00:15:00 00:15:00 00:05:00 00:15:00 00:05:00 00:15:00 00:15:00 00:04:50 00:15:00 00:15:00 00:05:00 00:15:00 00:05:00 00:10:01 00:10:01 00:34:57 19-JUL-2005 14:53:07 Selected: 12. Used: 14. REMAINING TIME shows the amount of time remaining until the next timeout mark. Possible values are: o U user specific timeout value o T a timeout is pending. • • • • • • ID shows the internal user identification.-. ES_ID . START DATE/TIME shows the starting date and time of the entry. [NO]ET_SYNC [NO]ET_SYNC This option controls the behaviour of the FEOF=PLOG function. UQ. the PLOG isn't switched and no checkpoint is written. ICQ. It must be specified before specifying FEOF=PLOG.ES_ID = number 19 This function influences the output of the DISPLAY options CQ. which can be considerably faster with very large databases than using ADABCK. LOCK. STOPUSER. Example The following scenario shows a backup and restore using a third-party backup tool (tar is not a real alternative. The default is NOET_SYNC. CANCEL.g.tar ASSO* DATA* % adaopr dbid=1 ext_backup=continue # external dump . ADADBM) can be started the functions SHUTDOWN. UQ_TIME_LIMITS. EXT_BACKUP EXT_BACKUP = [PREPARE | CONTINUE | ABORT] This function is used to backup a database using an external backup system. The following actions are performed: • • • • open a new PLOG with a new session number re-enable non-activity timeout checks re-enable update utilities wake up all waiting users (start of new transactions) The keyword ABORT is used to abort an external backup for which a PREPARE has already been issued. In this case. Refer to the FEOF=PLOG function for more information. UQ_FULL. UQ_FILES. During this phase. The keyword PREPARE prepares the database for backup. HQ. the following restrictions apply: new transactions will be stalled no updating utility functions (e. UNLOCK and FEOF=PLOG are not permitted once the EXT_BACKUP = PREPARE call has finished processing • all non-activity timeout checks are disabled • • • The keyword CONTINUE is used to resume normal database operations following completion of the external backup. Only entries with the specified environment-specific ID are displayed. and is used for demonstration purposes only): Dumping the database % adaopr dbid=1 ext_backup=prepare % tar cvf backup. Meaning The FEOF command will be rejected if the keyword PLOG is used while running ADAREC REGENERATE = * (see ADAREC for more detailed information).5. (timestamp) (timestamp) (timestamp) (timestamp) FEOF FEOF = (keyword [. then the command "adaopr db=1 et_sync feof=plog" results in the PLOGs PLG. session 20 started. ICQ. %ADANUC-I-EXTBPREP. UQ_FILES. and a new extent of the same PLOG will be created. %ADANUC-I-DBSTART. .tar # external restore % adastart 1 % adarec dbid=1 regenerate=* plog=21 ADANUC log file %ADANUC-I-DBSTART.0005 and NUCPLG. session 21 started. Example (PLOG is on raw device): if the current PLOG is PLG. The PLOG number is not incremented and the users do not have to be synchronized at ET status. %ADANUC-I-EXTBCONT. whereas the command "adaopr db=1 noet_sync feof=plog" results in the PLOGs NUCPLG. Database 1. continue from external backup. This depends on the [NO]ET_SYNC option: If ET_SYNC is specified: The current protection log file (PLOG) will be closed when all currently active ET logic users have come to ET status. the log file(s) are closed and a new log file is created.6. and a new PLOG is created with the next higher PLOG number. UQ_FULL and UQ_TIME_LIMITS.5(2).0005. Only entries related to the specified file number are displayed.20 Restoring the database % tar xvf backup. UQ.5 and PLG.0005(2). Keyword CLOG closes command log file. Database 1. whereas the command "adaopr db=1 noet_sync feof=plog" results in the PLOGs PLG. PLOG If NOET_SYNC is specified: The current PLOG extent will be closed when the next PLOG block is written. closes protection log file.keyword]) In accordance with the keywords specified. FILE FILE = number This influences the output of the DISPLAY options HQ.5(1) and PLG. preparing for external backup.0005(1) and NUCPLG.0006. Example (PLOG is in file system): if the current PLOG is NUCPLG. then the command "adaopr db=1 et_sync feof=plog" results in the PLOGs NUCPLG. For users who have one or more files to be locked in their open file list. [UN]LOCK [UN]LOCK = (number [. Refer to the description of the ADAOPR STOP parameter for more details. but keeps the command log file open Meaning If the nucleus was started with LOGGING=OFF and buffer logging is requested..number]. HQ. The specified files are locked for all non-utility use. The following keywords can be used: Keyword CB FB RB SB VB IB IO OFF Enables control block logging Enables format buffer logging Enables record buffer logging Enables search buffer logging Enables value buffer logging Enables ISN buffer logging Enables I/O list logging Stops logging of all buffers. Only entries related to the specified ISNs are displayed.keyword].. ICQ. a STOP <user-ID> command is issued internally..number] [..number] ] . UQ_FULL and UQ_TIME_LIMITS. LOGGING LOGGING = (keyword [. Adabas utilities can use the file(s) normally.) This parameter starts command logging for the buffers specified in the list of keywords.number [.21 ID ID = number This function influences the output of the DISPLAY options CQ. Only entries related to the specified internal ID are displayed. UQ. LOGIN_ID LOGIN_ID = number .) The file(s) specified by the file number(s) are locked or unlocked... ) This function influences the output of the DISPLAY option HQ. then the CLOG file will be created. UQ_FILES. ISN ISN = ( number [. This defines the maximum limit of ET command grouping before the PLOG buffers are written back to disk.22 This function influences the output of the DISPLAY options CQ. users who were already active when OPTIONS=UTILITIES_ONLY was specified can continue processing normally. OPTIONS OPTIONS = (keyword[. UQ_FULL and UQ_TIME_LIMITS. UQ. however. NISNHQ NISNHQ = number This parameter specifies the maximum number of records that can be placed into hold at any time by a single user. OPTIONS=NOUTILITIES_ONLY.keyword]) The available keywords are: Keyword [NO]LOCAL_UTILITIES Meaning If LOCAL_UTILITIES is specified.e. . ICQ. Only entries for the specified node are displayed. HQ. If UTILITIES_ONLY is selected. If the specified value is less than the corresponding high-water value. If you want exclusive utility control over files or the entire database. a warning is issued. the maximum value is 500. The minimum value is 1.g. Note. Only entries with the specified login ID are displayed. NODE_ID NODE_ID = string This function influences the output of the DISPLAY options CQ. HQ. that this restriction only applies to new users. UQ_FILES. where 0 means unlimited. use the LOCK function of ADAOPR instead. If the specified value is less than the corresponding high-water value. UQ. e. UQ_FULL and UQ_TIME_LIMITS. the nucleus rejects all remote utility calls. MGC MGC = number This parameter specifies the maximum group-commit count. the Adabas utilities cannot be run from a remote node across a network. a warning is issued. all calls other than for utilities will be rejected. and the final IO has been performed. The minimum value is 0. ICQ. If this limit is reached. UQ_FILES. all remaining users will be posted. i. [NO]UTILITIES_ONLY These options can be disabled using the prefix `NO'. the database section file (Adabas. Also refer to the ADAOPR FILE parameter. The information written may be used to analyze possible problems in the database's operation.23 RESET RESET = keyword RESET=HIGH_WATER resets the high water mark values to the value currently in use.APP. If a response check for an Adabas response code is enabled. The setting of the [NO]RESPONSE_ABORT option can only be changed before the RESPONSE_CHECK parameter. the SMP dump file is also written. Depending on the setting of the RESPONSE_ABORT option.xxx. The default is NORESPONSE_ABORT.xxx.number[-number]]. • if the NORESPONSE_ABORT option is set (default setting). RESPONSE_CHECK RESPONSE_CHECK = [(number[-number][.xxx. Also refer to the ADAOPR FILE parameter. Also refer to the ADAOPR FILE parameter. the nucleus continues running and the database section file (Adabas. See ADANUC and the environment variable ADA_CSA_DUMP for more information.hh:mm:ss) is written to the database's default directory.. the nucleus either aborts or continues operation: if the RESPONSE_ABORT option is set. See ADANUC and the environment variable ADA_CSA_DUMP for more information. The name of the SMP dump file is SMPPOS.)] This function enables the DBA to gather information if one of a list of Adabas response codes occurs. See ADANUC and the environment variable ADA_CSA_DUMP for more information. When the CSA dump file is written. if the RESPONSE_ABORT option is set. The same applies for XA_RESPONSE_CHECK. Refer to the RESPONSE_CHECK parameter for further information.RSPyyy. the database section file is written to disk if this response code occurs.xxx. the RESPONSE_ABORT option determines whether the nucleus aborts when one of the specified responses occurs (RESPONSE_ABORT).hh-mm-ss) is written to the database's default directory.hh:mm:ss) is written to the database's default directory. the nucleus continues running and the database section file (Adabas. Also refer to the ADAOPR FILE parameter. • if the NORESPONSE_ABORT option is set (default setting). • The database section file is also called the CSA dump file. the database section file (Adabas.RSPyyy.hh:mm:ss (UNIX platforms only). See ADANUC and the environment variable ADA_CSA_DUMP for more information.. [NO]RESPONSE_ABORT [NO]RESPONSE_ABORT If response checking is enabled with the RESPONSE_CHECK parameter of ADAOPR. • . or whether the nucleus resumes operation and a database section file is written to disk (NORESPONSE_ABORT).hh-mm-ss) is written to the database's default directory. . Users without or with "P" status. If this happens. Meaning . UQ_FULL. the Adabas session is terminated. Refer to the RESPONSE_ABORT option for further information.. ET-user updating is continued until the end of the current transaction for each user. In this case. When all update activity has ended as described above. 255. Only these files will be displayed by DISPLAY = FILE_IO. The response codes in question for ADALNK are: 9. display functions are still possible with ADAOPR but parameter modification commands are no longer permitted. 146-154. 40.keyword] . UQ_FILES. ICQ. No new users are accepted. use "RESPONSE_CHECK =" without arguments. no response is trapped and the nucleus continues operation.. STATUS STATUS = (keyword [.. UQ. 40.24 By default.)] This function enables the file level I/O statistics for the specified files. Note: Some response codes can be generated outside the nucleus (e. Note: Some response codes can be generated outside the nucleus (e. 241. 22. 252. The communication link to the database is cut but the shared memory is still held. by ADALNK and ENTIRE NET-WORK). they cannot be trapped by Adabas. ) This function influences the output of the DISPLAY parameter options HQ.g. The valid keywords are: Keyword [NO]TIMEOUT [NO]ET_STATUS [NO]PENDING_ET User without or with "T" status. 17.. they cannot be trapped by Adabas.number[-number]]. The response codes in question for ADALNK are: 9. SET_FILE_STATS SET_FILE_STATS = [(number[-number][. 146-154. To disable response trapping. Only entries in the specified state will be displayed. Users at "ET" status with open transactions. 17.g. UQ_TIME_LIMITS. SHUTDOWN SHUTDOWN This function terminates the Adabas session normally. 255. 22. If this happens. 241. by ADALNK and ENTIRE NET-WORK). The message "Stop handling started for n users" is displayed. OP command). Note: Utilities cannot always be stopped in this way. scratch the user type. and also whether the nucleus requires an explicit OP (open) command at the start of a user session. ET.) This parameter terminates the user with the specified ID (internal identification).number[-number]]. The actions that Adabas takes when a user is stopped depend on the user type.. SUQE. session closed session closed If a STOP command is issued for a user while running ADAREC REGENERATE = * it will be rejected (see ADAREC in this manual for more information). session closed session closed session closed Backout transaction. The abbreviation SUQE used in the table means "Stop user queue element".. TNAA TNAA = number This parameter sets the non-activity time limit (in seconds) for access-only users who have not explicitly specified a TNAA value in the OP command (see Command Reference. CLSE checkpoint SUQE. CLSE checkpoint session closed Adabas Actions with ADANUC OPTIONS=OPEN_REQUIRED session closed session closed Backout transaction. ET Status ET. The ID can be retrieved with DISPLAY = UQ. set response 9 for the next call. and consists of the following actions: release all Command IDs. CLSE checkpoint Backout transaction. ET with ET status EX. scratch the user ID. as shown in the following table. where "n" is the number of users who will be stopped. no ET Status EX EX. no ET status UT Adabas Actions without ADANUC OPTIONS=OPEN_REQUIRED For ID user: SUQE For non-ID user: session closed For ID user: SUQE For non-ID user: session closed Backout transaction. User Type ACC ET. . scratch the file list.25 STOP STOP = (number[-number][. SUQE SUQE. In any particular instance. UQ_FILES. a warning is issued. If the specified value is less than the corresponding high-water value. The minimum value is 20. the actual amount of time can vary from this value by up to 10 seconds. the maximum value is 2592000. The minimum value is 20.26 Note that the figure you specify for this parameter is only approximate. In any particular instance. OP command). Note that the figure you specify for this parameter is only approximate. Note that the figure you specify for this parameter is only approximate. UQ. TT TT = number This parameter sets the transaction time limit for ET logic users who have not explicitly specified a TT value in the OP command (see Command Reference. the maximum value is 2592000. The minimum value is 20. the maximum value is 2592000. HQ. UQ_TIME_LIMITS. TNAX TNAX = number This parameter sets the non-activity time limit (in seconds) for EXU and EXF users who have not explicitly specified a TNAX value in the OP command (see Command Reference. In any particular instance. Note that the figure you specify for this parameter is only approximate. OP command). ICQ. the actual amount of time can vary from this value by up to 10 seconds. OP command). . USER_ID USER_ID = string This function influences the output of the DISPLAY parameter options CQ. Only entries in the specified user ID will be displayed. the maximum value is 2592000. TNAE TNAE = number This parameter sets the non-activity time limit (in seconds) for ET logic users who have not explicitly specified a TNAE value in the OP command (see Command Reference. the actual amount of time can vary from this value by up to 10 seconds. the actual amount of time can vary from this value by up to 10 seconds. The minimum value is 20. In any particular instance. UQ_FULL. the nucleus either aborts or continues operation: if the RESPONSE_ABORT option is set. 0 means that Adabas will dynamically choose an appropriate value.hh:mm:ss) is written to the database's default directory.. • if the NORESPONSE_ABORT option is set (default setting). Refer to the RESPONSE_ABORT option for further information. If a response check for an XA response code is enabled. Note that "WRITE_LIMIT=" (keeping the equals sign but omitting the number) is equivalent to "WRITE_LIMIT=0". • By default. use "XA_RESPONSE_CHECK =" without arguments.XAyyyy.. XA_RESPONSE_CHECK XA_RESPONSE_CHECK = (keyword [. The minimum value is 0 and the maximum value is 70. the nucleus continues running and the database section file (Adabas.. ) This function enables the DBA to gather information if one of a list of XA response codes occurs.xxx. no response is trapped and the nucleus continues operation.keyword] . the database section file (Adabas.27 WRITE_LIMIT WRITE_LIMIT = [number] This parameter specifies the percentage of modified blocks permitted in the buffer pool before an implicit buffer flush is taken.hh:mm:ss) is written to disk (refer to the ADAOPR FILE parameter for further information). The information written may be used to analyze possible problems in the database's operation.xxx. To disable response trapping. Depending on the setting of the RESPONSE_ABORT option. the database section file is written to disk if this response code occurs. The following keywords are supported: XA_RBROLLBACK XA_RBCOMMFAIL XA_RBDEADLOCK XA_RBINTEGRITY XA_RBOTHER XA_RBPROTO XA_RBTIMEOUT XA_RBTRANSIENT XA_NOMIGRATE XA_HEURHAZ XA_HEURCOM XA_HEURRB XA_HEURMIX XA_RETRY . 28 XAER_ASYNC XAER_RMERR XAER_NOTA XAER_INVAL XAER_PROTO XAER_RMFAIL XAER_DUPID XAER_OUTSIDE XA_RBROLLBACK .
Copyright © 2024 DOKUMEN.SITE Inc.