Home

SQL/MX Connectivity Service Administrative Command Reference

1. This example is a set of adds showing at least one add for each EVAR type The full object name in the first command is the default for subsequent commands Each command produces a confirmation not shown Note Single and double quotes are required where shown gt gt mode mxcs CS gt ADD EVAR SAS TDM_Default_DataSource EMPLOYEE type define valu CLASS MAP FILE S DATA0O1 PERSNL EMPLOYEE CS gt ADD EVAR DEPT type define value CLASS MAP FILE SDATA02 PERSNL DEPT CS gt ADD EVAR HIST_NO_STATS_ROWCOUNT value 123456789 CS gt ADD EVAR HIST_NO_STATS_UEC value 99 CS gt ADD EVAR QUERY _CACHE value 10000 CS gt ADD EVAR QUERY CACHE MAX VICTIMS value 100 CS gt ADD EVAR QUERY_CACHE_STATISTICS value ON CS gt ADD EVAR QUERY_CACHE_STATISTICS_FILE value home testcachefiles myStats CS gt ADD EVAR TIMEOUT value RESET CS gt ADD EVAR SCRATCH_DISKS value Sdata0l data02 testsys data03 CS gt ADD EVAR TIMEOUT prefix control table value 3000 CS gt ADD EVAR PERSNL JOB MDAM prefix control table value OFF CS gt ADD EVAR ESTIMATED COST type rmp limit 123456 action STOP CS gt ADD EVAR CATALOG type set value TANDEM_SYSTEM_NSK CS gt ADD EVAR SCHEMA type
2. add evar sratch_disks Misspelled EVAR name to demonstrate an error add evar scratch_disks add evar EMP type define info ds detail info evar j info ds start service start ds Test_DSN info service detail info ds detail info server info server 1 3 stop ds delete ds stop service Sas This is an example of running the commands and messages that result Operator permissions are required to execute add start stop and delete so it is assumed the user has this permission No security permissions are necessary to run info This example starts the service object SAS using the MXOAS command at the TACL prompt where i indicates that the service enters the stopped state after initialization no servers start until the DS and service are started volume Ssystem zmxodbc run mxoas name Sas nowait term zhome tcp ztc0 i pn 21000 SQL MX Connectivity Service Administrative Command Reference 526350 005 A 1 Example Commands and Objects This example starts MXCI and verifies that the service started properly mxci Hewlett Packard NonStop TM SQL MX Conversational Interface 2 0 c Copyright 2003 Hewlett Packard Development Company LP gt gt mode mxcs CS gt info service as INFO SERVICE ODBC AS Report PName State SPid TCP IP PN Port Last Updated Type SAS STOP 1 386 ZTCO 21000 Mar 26 13 37 AS Z3445 AVL 1 394
3. membername is the NonStop OS user logon name with no aliases permitted PERM perm value is the permission value to be assigned this user The default is either User or Operator depending on what is already assigned No error is reported if the explicate permission is the same as the current permission and no change occurs The permission keyword Operator is equivalent to Oper Considerations ALTER USER ALTER USER is a sensitive command e The asterisk wild card is not supported Only the SUPER SUPER user can execute this command SUPER SUPER and DEFAULT users cannot be altered Example ALTER USER This example changes the database permission for the named user to the other value CS gt alter user grouptst george ALTER USER ODBC GROUPTST GEORGE Successful SQL MX Connectivity Service Administrative Command Reference 526350 005 7 3 Object User Commands DELETE USER DELETE USER This command deletes one user name and permissions from the MXCS configuration database access list Command syntax is DELETE USER obj name obj name system name groupname membername system name is the name of a group of up to 16 CPUs with the same Expand address system name and service name identify one instance groupname is the NonStop OS group logon name membername is the NonStop OS user logon name with no aliases permitted Considerations DELETE USER DELETE
4. Terms used in info server reports are defined as listed Cl Client Cl User ID NonStop OS user ID used by client application to connect to server if connected Cl Proc ID Client process ID if connected Cl App ID Client application ID if connected Last State Change Time connection opened or idle state began Port NonStop TCP IP port number PName Process name State Service state SPid Service program ID CPU process number TCP IP PN NonStop TCP IP process name use SCF to find IP address SQL MX Connectivity Service Administrative Command Reference 526350 005 4 4 Object Server Commands STOP SERVER STOP SERVER This command puts the server in the stopping state The actual termination occurs at different times depending on the stop mode attribute you specify Check on progress by using the INFO SERVER command Command syntax is STOP SERVER obj name AFTER stop mode obj name system name Sservice name Sserver name system name is the name of the current system of up to 16 CPUs with the same Expand address and where the target MXCS process is running syst em name and service name identify one service instance service name is the name of the MXCS association server process that owns this server server name is the name of the MXCS server process to be stopped It must not be an association or configuration server It cannot be the asterisk wil
5. Note ds name is an SQL identifier and is therefore case sensitive When using lowercase characters enclose ds name in quotes to preserve the lowercase characters Failure to do so causes ds name to be automatically uppercased during command execution which can cause errors Enter the default ds name aS TMD Default DataSource evar name Is the name of the EVAR to be displayed It can be the asterisk wild card If the EVAR name is an asterisk and the type is a11 the EVARs for this DS are displayed If the EVAR name is an asterisk and a type other than a11 is specified the EVARs of that type for this DS are displayed If the EVAR name is specified and a type other than a11 is specified that EVAR for that DS is displayed The EVAR name is an SQL identifier and requires double quotes in some cases When the type is a define the name can optionally contain a leading equal sign with or without quotes The name is always set to uppercase even when enclosed in quotes TYPE type name is one of the valid types from the table in EVAR Types on page 6 1 The default type is control SQL MX Connectivity Service Administrative Command Reference 526350 005 6 11 Object EVAR Commands Considerations INFO EVAR Considerations INFO EVAR e INFO EVAR is not a sensitive command The asterisk wild card is supported for evar name e INFO EVAR displays every EVAR with a name match If more than one match is found
6. Oom VST003 vsd Valid Command and Object Type Pairs All MXCS administrative commands do not support all objects types The supported commands and object types are listed with X indicating valid pairs such as ADD DS Object Type Command DS EVAR Server Service User ADD X X X ALTER X X X DELETE X X X INFO X X X X X START X X STOP X X X VERSION X Command Rules and General Syntax Command Termination Each MXCS administrative command ends with a semicolon Several commands can be on one input line or one command can span several input lines Use tabs spaces and new lines to separate parameters in a command SQL MX Connectivity Service Administrative Command Reference 526350 005 2 3 MXCS Commands and Objects Fields or Tokens in Commands Fields or Tokens in Commands All fields or tokens in a command belong to one of these types Keyword Single word without quotation marks uppercase or lowercase not case sensitive alohanumeric characters A through Z or a through z plus 0 through 9 Called key value when used as a value of an attribute Number Single word numeric characters 0 through 9 with sign or no spaces and no commas System name Single word beginning with a backslash uppercase or lowercase not case sensitive alphanumeric characters A through Z or a through z plus 0 through 9 Process name Single word beginning with dollar sign u
7. Reports errors if the ODBC facility of MXCS is not running when needed O O O O OOO Architecture Overview The MXCS administrative command library MACL is the software component inside MXCI that supports the MXCS administrative commands described in this guide MACL is discussed only to show how the MXCS administrative commands are processed and to assist you in understanding error messages that might appear Figure 1 1 on page 1 3 shows how the MACL library fits in the system architecture with MXCS MXCI and the SQL MX database MACL links with MXCI and uses many of the existing generic features of the MXCI command line interface MXCI manages command entry and passes commands to MACL for processing MXCI also displays report lines and error messages when a command is processed MXCI also supports execution of SQL statements through the SQL engine directly or through the report writer When you start MXCI some but not all administrative commands are available when ODBC is not running on the system Some of these commands require that the ODBC association server be operational However you can always configure a DS EVAR and user MXCI is not required to be running while MXCS runs so you can run MXCl for only as long as you need to maintain a session Before entering any MXCS SQL MX Connectivity Service Administrative Command Reference 526350 005 1 2 MXCS Architecture Overview Architecture Overview administrative command se
8. The last line of the report Totals for Service displays only if more than one active DS exists Terms used in info service reports are defined as listed PName Process name State Service state SPid Service program ID CPU process number TCP IP PN NonStop TCP IP process name use SCF to find IP address Port NonStop TCP IP port number Last Updated Last state change time Type Server type AS Association server CFG Configuration server SQL MX Connectivity Service Administrative Command Reference 526350 005 3 3 Object Service Commands START SERVICE START SERVICE This command starts The target service after the TACL command RUN MXOAS has initiated the process e All DSs that auto start The initial servers associated with a started DS After service starts clients can begin connecting to the servers Command syntax is START SERVICE obj name obj name system name Sservice name system name is the name of the current system of up to 16 CPUs with the same Expand address and where the target MXCS process is running syst em name and service name identify one service instance service name is the name of the MXCS association server process of the service to be started This name must be an association server process that is in the stopped state Considerations START SERVICE START SERVICE is a sensitive command The asterisk wild card is not suppor
9. 1 to 199 and SYSTEM_DEFAULT which is the association server s process priority priority val SYSTEM_DEFAULT number Trace OFF is a flag for activating the server trace facility in all servers using this DS and started by this service The Trace flag is not a permanent setting is not stored in the configuration database and is not retained through a service shutdown It is set as specified on this DS for the current service or all services when the asterisk wild card is used for the service name Trace data is written to the collector specified when the service is started Use this flag without the OFF option to turn it ON The default value is OFF when the attribute is not used CpuList cpu val is an SQL string literal with multiple values enclosed in single quotes containing the list of CPU numbers where the service can start servers for this DS When you use this parameter specify all requested CPUs Valid values are 0 to 15 and ALL The value ALL specifies all available CPUs on the system where the service is running When to using CPUList note e Duplicate CPU numbers are ignored e The order of CPU numbers from CPUList appears as the next higher sequential CPU number in the list and not in the order entered on the command line SQL MX Connectivity Service Administrative Command Reference 526350 005 5 4 Object DS Commands ADD DS Nonexistent CPU numbers are not reported Because a CPU ca
10. 526350 005 2 8 MXCS Commands and Objects Command Caveats Command Caveats Use care when specifying a backslash and dollar sign in commands when input is not from the command line or an OBEY command file These characters have special meaning to the OSS shell Output Report Syntax and Conventions All output report lines contain a maximum of 79 characters with longer lines automatically folded Because a DS name can be up to 128 characters a long DS name is the most likely cause of output report format problems Field width for DS names is limited to 32 characters Therefore folding occurs for names longer than that limit Obey the 32 character limit where possible All long lines fold to the next line at a space character nearest the end of the line with the remainder of the line indented four spaces Long DS names appear as in these examples Start Server Limits Server Usage Name State Auto Max Init Idle Con Avl Tot TDM_Default_DataSource STARTED ON 5 1 1 0 1 1 DS2 STOPPED OFF 5 3 3 0 0 0 ThisDataSourceNamelIsLongerThan32CharactersButLessThan79Characters STOPPED OFF 10 5 2 0 0 0 ThisDataSourceNameIsLongerThan32CharactersAndLongerThan7 9CharactersAndMakesTheRe portsLookReallyBAD_BAD_BAD_ReallyBAD_ReallyBAD STOPPED OFE 5 1 2 0 0 0 Attributes display in either tables or two column lists with two column lists period filled between the attribute name and the value The first line of all repor
11. COMNINEOSCAG RS steels has aeae teens caters OFF SQLEXE CULES TAT ise hi See vee ar lesa eee els OFF SQL MX Connectivity Service Administrative Command Reference 526350 005 A 2 Example Commands and Objects S SSTOnINFOSt AE ea sie eke woe ah EERE OFF SOLEXeCD1 TEGESEACSS a i eeehe Seeder ele sre 8 ON SQLSEMUSC AC esa bse cs oss bale whe teas Suse OFF SQLPECCHS UAE so asi sie sacle al Wis es Nite aie ON CS gt info evar type all INFO EVAR ODBC SAS TEST_DSN Report Resource anagement Policies ESTIMATED COST Limit 500 Action STOP Defines ADD DEFINE EMP CLASS MAP FILE DATA01 PERSNL EMPLOYEE Controls CONTROL QUERY DEFAULT TIMEOUT RESET CONTROL QUERY DEFAULT SCRATCH_DISKS S data0l data02 ODBC data03 Sets None This example displays all DSs on the system CSrinto ds INFO DS ODBC SAS Begun Start Name State Auto TDM_Default_DataSource STARTED ON EST_DSN STOPPED OFF Cmd processed 2 objects 0 failed Server Limits Server Usage Max Init Idle Con Avl Tot 5 1 T 0 1 1 5 2 3 0 0 0 This example starts the service and the DS in the service As CS gt start service START SERVICE ODBC AS Successful CS gt start ds Test_DSN START DS ODBC SAS TEST_DSN Successful This example verifies the results of starting the servic
12. INT ERRUPTS A group of items enclosed in brackets is a list from which you can choose one item or none The items in the list can be arranged either vertically with aligned brackets on each side of the list or horizontally enclosed in a pair of brackets and separated by vertical lines For example FC num num text K X D address Braces A group of items enclosed in braces is a list from which you are required to choose one item The items in the list can be arranged either vertically with aligned braces on each side of the list or horizontally enclosed in a pair of braces and separated by vertical lines For example LISTOPENS PROCESS appl mgr name process name ALLOWSU ON OFF Vertical Line A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces For example INSPECT OFF ON SAVEABEND SQL MX Connectivity Service Administrative Command Reference 526350 005 xi About This Manual Notation for Messages Ellipsis An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times For example M address new value O 1 2 3 4 5 6 7 8 9 An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times For example s char Punctuation Paren
13. is the NonStop OS user login with no aliases permitted This component is an SQL identifier data type but is always set to uppercase after the command processes it see Fields or Tokens in Commands on page 2 4 If you use the asterisk or question mark in a name enclose it in single or double quotation marks or it is flagged as an invalid use of a pattern The only valid pattern is an asterisk alone with no quotes which generally indicates all DS Name and EVAR Name The DS and EVAR name are not case sensitive unless they are enclosed in double quotes To eliminate the need for double quotes avoid spaces punctuation and lowercase characters When necessary include a double quote in such a name by doubling it A backslash is accepted as a character and not considered an escape character An example of a DS name with embedded special characters is SAS ds n ame specifies DS ds n ame Default Object Name Use the default when object name components are long and difficult to type To ensure all cases are well defined follow these guidelines e After you use an object name it is retained until you enter another name component of the same type When you use an object name the obj type field on the command defines the object type of the last specified component of the name For example the commands info service z0123 andinfo server z0123 are well defined The first example wil
14. no warning is generated e INFO EVAR displays the EVARs in the order that they are applied When an EVAR does not fit on a 79 character line it is folded at the most reasonable blank space if possible with subsequent lines indented four spaces Example INFO EVAR This example displays an EVAR of type define with the name GROUP in the DS TDM_Default_DataSource You can use the equal sign in the name but it is not required CS gt info evar TDM_Default_DataSource GROUP type define INFO EVAR ODBC TDM Default DataSource GROUP Report ADD DEFINE GROUP CLASS MAP FILE SDATA03 PERSNL GROUP This example uses wild cards and is type a11 This is the default DS and it has no EVARs defined CS gt info evar TDM_Default_DataSource type all INFO EVAR ODBC TDM_Default_DataSource Report Resource Management Policies None Defines None Controls None Sets None This example uses wild cards and the type is a11 This DS has some of each EVAR defined Note the control table EVARS CS gt info evar TDM_Default_DataSource type all INFO EVAR ODBC TDM_Default_DataSource Report Resource Management Policies ESTIMATED COST Limit 123456 Action STOP Defines ADD DEFINE EMPLOYEE CLASS MAP FILE SDATA01 PERSNL EMPLOYEE ADD DEFINE DEPT CLASS MAP FILE SDATA02
15. 1 LastStateChg Oct 18 11 43 THASEVU POAT Es se ieee eee Sete eer bor oe Not Set TALES SEM Ep eane cond pis AEE parton E T 5 TALSTIMEOUCS oe cee ce ee 8 SYSTEM_DEFAULT Max Server aae e SPs ate eae esi wa 20 COMM TIME OUE aa Seer ote se whens R eiS 60 TRL SOTVC roren na ea e oi bie 0 eles ee 10 StartA tomat iCase side ea Ge ee Meas OFF ra Ekee Sra exe cota E E cara recetiss tas OFF SOLPLEPALTSSE Ab is arse see orari a Seca ts ON COMNINLTO SEAT sa as a te ave ese eters ws ON SOLEXSCUUCSEAE en we Sessa einate e S ace oes ON S esslon nfoStat views Sew a ON SQLExecDirectStat 00 ON SOUS CMES C ait wig enr cease wees eee as seas ON SQLEFSUCHS CAG oi s ea ee ee srang EEE ON Cmd Processed 2 objects 0 failed Terms used in info Sta Sta Max Ini Idl Con Avl Tot DS reports are te DS state rtAuto Automatic DS start when its association server process starts Upper limit of operational servers for this service on this DS E Number of idle servers to start when DS starts e Lower limit of idle servers for this service on this DS Number of connected servers Available servers for this service on this DS registered minus connected servers Number of registered servers Terms used in info Cpu Ini Cur Con Ava Las Las Id Id List tPri rentState nectedServers ilableServers tStateChg tUpdate eserver eTimeout Max Con Ini
16. DS name 2 6 EVAR name 2 6 groupname 2 7 system name 2 6 user name 2 7 server name 2 6 service name 2 6 Object types default prefix 6 1 Objects command pairing 2 3 DS ownership 2 2 list of 2 1 2 2 Output report syntax and examples 2 9 P Prompt 2 12 Prompt for MXCS 1 4 R Report error 1 7 1 9 S Server name object syntax 2 6 Service name object syntax 2 6 START command command syntax 3 4 object DS 5 18 object SERVICE 3 4 Starting MXCS 2 12 STOP command command syntax 3 5 object DS 5 19 object SERVER 4 5 object SERVICE 3 5 Syntax case sensitivity 2 5 command rules 2 3 output report 2 9 SQL MX Connectivity Service Administrative Command Reference 526350 005 Index 2 Index System name object syntax 2 6 T Terminal prompt MSCS 1 4 Terminate MXCS mode 1 4 Terminating character command line 2 3 U User name object syntax 2 7 V VERSION command command syntax 3 7 object SERVICE 3 7 W Wild card asterisk only 1 4 Special Characters server name object syntax 2 6 service name object syntax 2 6 SQL MX Connectivity Service Administrative Command Reference 526350 005 Index 3
17. MX Reference Manual Specialized Guides SQL MX Queuing and Publish Subscribe Services SQL MX Installation and Management Guide SQL MX Query Guide SQL MX Data Mining Guide SQL MX Connectivity Service Manual SQL MX Report Writer Guide SQL MX Online Help SQL MX Guide to Reference Help Visual Query Planner Help Stored Procedures in Java 0 vst001 vsd Messages Glossary NSM web Help Help Help Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text By clicking a passage of text with a blue underline you are taken to the location described For example SQL MX Connectivity Service Administrative Command Reference 526350 005 x About This Manual General Syntax Notation This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3 2 General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual UPPERCASE LETTERS Uppercase letters indicate NSK keywords and reserved words Type these items exactly as shown Items not enclosed in brackets are required For example MAXATTACH lowercase italic letters Lowercase italic letters indicate variable items that you supply Items not enclosed in brackets are required For example file name Brackets Brackets enclose optional syntax items For example TERM system name Sterminal name
18. MX Connectivity Service Administrative Command Reference 526350 005 5 9 Object DS Commands ALTER DS InitPri priority val is the initial system priority used to start a new server on this DS The valid values are 1 to 199 and SYSTEM_DEFAULT number which is the association server process priority priority val SYSTEM DEFAULT number Trace OFF is a flag for activating the server trace facility in all servers using this DS and started by this service The Trace flag is not a permanent setting is not stored in the configuration database and is not retained through a service shutdown It is set as specified on this DS for the current service or all services when service name is the asterisk wild card Trace data is written to the collector specified when the service is started Use this flag without the OFF option to turn it ON The default value is not changed when the attribute is not used Changing this flag affects currently running servers started by this service CpuList cpu_val is an SQL string literal in single quotes if specifying more than one value containing the list of CPU numbers where the service can start servers for this DS the next CPU is selected round robin When you use this parameter all requested values must be specified again The valid values are 0 to 15 and ALL which specifies all available CPUs on the system where the service is running Duplicate numbers are accepted Becaus
19. MXCS configuration database For information on managing these objects see Section 7 Object User Commands O O O 0 0 Basic security rules are Only the user who installed SQL MX super ID user SUPER SUPER can modify the user list Only users who have the operator permission in the user list can execute sensitive commands The SUPER SUPER user always has operator permissions which cannot be changed Everyone has the user permission in the user list by default so anyone can execute informational commands The generic user PUBLIC always has user permissions which cannot be changed or removed Adding individual users with the user permission is permitted but is currently unnecessary Note Use sensitive commands with caution to prevent disrupting users Grant the operator permission only to users trained in ODBC concepts If several users with the operator permission are changing things at the same time maintaining consistency of object definitions can be at risk Example MXCS Configuration The next list of objects and attributes defines the static portion of the MXCS configuration that appears in all examples in this manual You start MXCS from a TACL prompt with a command line that specifies the service name SAS in this example the SQL MX Connectivity Service Administrative Command Reference 526350 005 2 10 MXCS Commands and Objects Related Commands NonStop TCP IP address TCP driver process name t
20. Manual Related Documentation The NSM web and Visual Query Planner help systems are accessible from their respective applications You can download the Reference Messages and Glossary online help from the SYSTEM ZMXHELP subvolume or from the HP NonStop Technical Library NTL For more information about downloading online help see the SQL MX Installation and Management Guide These manuals are part of the SQL MP library of manuals and are essential references for information about SQL MP Data Definition Language DDL and SQL MP installation and management Related SQL MP Manuals SQL MP Reference Manual Describes the SQL MP language elements expressions predicates functions and statements SQL MP Installation and Describes how to plan install create manage an Management Guide SQL MP database Describes installation and management commands and SQL MP catalogs and files SQL MX Connectivity Service Administrative Command Reference 526350 005 ix About This Manual Notation Conventions This figure shows the manuals in the SQL MxX library Programming Manuals Introductory Guides SQL MX Comparison Guide for SQL MP SQL MX Programming Manual for C and COBOL SQL MX Programming Manual for Java SQL MX Quick Start Users Reference Manuals a SQL MX Connectivity Service Adminis trative Command Reference SQL MX Reference Manual SQL MX Messages Manual SQL MX Glossary Data Loader
21. PERSNL DEPT Controls CONTROL QUERY DEFAULT HIST_NO_ STATS ROWCOUNT 123456789 SQL MX Connectivity Service Administrative Command Reference 526350 005 6 12 Object EVAR Commands Example INFO EVAR CONTROL QUERY DEFAULT HIST_NO_STATS_UEC 99 CONTROL TABLE TIMEOUT 3000 CONTROL TABLE PERSNL JOB MDAM OFF Sets SET CATALOG TANDEM SYSTEM NSK SET SCHEMA PUBLIC ACCESS _ SCHEMA This example uses a compound name It assumes the same DS as the last example and uses the default type CS gt info evar PERSNL JOB MDAM INFO EVAR ODBC TDM_Default_DataSource PERSNL JOB MDAM Report CONTROL TABLE PERSNL JOB MDAM OFF SQL MX Connectivity Service Administrative Command Reference 526350 005 6 13 Object EVAR Commands Example INFO EVAR SQL MX Connectivity Service Administrative Command Reference 526350 005 6 14 Ey Object User Commands This section describes the MACL commands that are available to an MXCS administrator for the user object see Valid Command and Object Type Pairs on page 2 3 ADD USER on page 7 2 ALTER USER on page 7 3 e DELETE USER on page 7 4 INFO USER on page 7 5 Only the NonStop OS super ID user SUPER SUPER or its alias is registered in the MXCS configuration database with the grant permission in addition to the operator permission See Sec
22. Report DS Name Test2 PName State SPid TCP IP PN Port Last State Chg Remote System Nam Z0481 AVL 1 394 ZTCO 21002 Jan 22 12 15 DS Name TDM _Default_DataSource PName State SPid TCP IP PN Port Last State Chg Remote System Nam Z0483 CON 0 404 ZTCO 21009 Jan 22 12 55 TUSER1 P1 Z1114 AVL 0 387 ZTCO 21021 Jan 22 12 16 Z1115 AVL 1 361 ZTCO 21022 Jan 22 12 16 Cmd Processed 4 objects 0 failed Detailed report for a server that is not connected CS gt info server SAS Z0481 detail INFO SERVER ODBC S AS Z0481 Report DETAIL DS Name TDM _Default_DataSource PName State SPid TCP IP PN Port Last State Chg Remote System Nam Z0481 AVL 0 387 ZTCO 21021 Jan 22 12 16 Cl USS IDa ia ee Eaa Not Avail Gil App N men tarta dne shes Not Avail Cl PEOG TD iiss snc atin eee ec Not Avail SQL MX Connectivity Service Administrative Command Reference 526350 005 4 3 Object Server Commands Example INFO SERVER Detailed report for a server connected to a PC application Microsoft Access CS gt info server SAS Z0483 detail INFO SERVER ODBC SAS Z0483 Report DETAIL DS Name TDM _Default_DataSource PName State SPid TCP IP PN Port Last State Chg Remote System Nam Z0483 CON 0 404 ZTCO 21009 Jan 22 12 55 TXNUSER1 P1 Gli Usei Der eerten Naaa swdevl userl CI App Namera its aces ate eos MS Access GCL Proc IDo tisha bisa dist Bate an a E See gS 836
23. SQL MX Database Engine DS1 y EVAR1 y EVAR2 On Disk On Disk On Disk DS2 gt EVAR3 On Disk On Disk DS3 On Disk SQL MX Database Tables VST004 vsd The servers owned or started by Service A all run on CPU 5 Service B has two servers on CPU 9 and one server running on CPU 11 Using the cpuList parameter each DS defines where the service can start servers using that DS It is possible that DS 1 has only CPU 5 in its list while DS 2 has both CPU 5 and 9 in its list and DS 3 has CPU 9 and 11 To accurately determine which CPUs are permitted display the detailed information about each DS by using one of the MXCS administrative commands SQL MX Connectivity Service Administrative Command Reference 526350 005 1 6 MXCS Architecture Overview Error Message Overview All MXCS objects can be viewed or manipulated with MACL commands supported by MXCI Through MACL and the configuration client library MXCI establishes and terminates connections to the process that makes up the logical service and in some cases connections directly to the MXCS configuration database Although Figure 1 2 shows one system an Expand network can connect to other systems Each system must have its own copy of the configuration database MXCI and its own MXCS services Server objects owned by one service can run on any CPU specified by the DS definition Service objects can al
24. Server nTimeout tServer DS reports with the detail option are List of CPUs that the service can start the servers on round robin Initial process priority to start a new server on this DS Current state of the data source Number of connected servers Servers available for this service on this DS Time the connection opened or the idle state began Last time a DS attribute was updated Lower limit of the idle servers for this service on this DS Number of minutes a server waits in the available state before stopping itself Upper limit of servers for this service on this DS Number of minutes a client server connection remains idle before the server terminates Number of idle servers to start when the DS starts SQL MX Connectivity Service Administrative Command Reference 526350 005 5 18 Object DS Commands StartAutomatic Trace SQLPrepareStat ConninfoStat SQLExecuteSta SessionInfoStat SQLExecDirectStat SOLStmtStat SQLFetchStat Examples INFO DS Automatic DS start when its associated server process starts Activates server trace facility in all servers started by and using this DS SQL prepare statistics gathered when a PREPARE statement is received Connection information statistics gathered when a connection is established SQL execute statistics gathered when an EXECUTE statement is received Session information statistics gathered when a session is term
25. an attribute Causes an error Command Syntax Case Command syntax is case sensitive only when enclosed in single or double quotes Object Name Components An object name has one to four components separated by periods No space or carriage returns are permitted around period separators The components of an object name depend on which object type is being addressed A component can also be defaulted to the last specified value on an earlier command Some commands permit the asterisk wild card to be used as a component name SQL MX Connectivity Service Administrative Command Reference 526350 005 2 5 MXCS Commands and Objects Object Name Components General syntax is For service system name service name For DS system name service name ds name For EVAR system name service name ds name evar name For server system name service name server name For user system name groupname membername See individual commands for specific syntax formats system name is the name of the current system of up to 16 CPUs with the same Expand address and where the target MXCS process is running The default is the system where MXCI is executing This component is a system name data type see Fields or Tokens in Commands on page 2 4 Sservice name is the name of the service the target MXCS association server process name Using an asterisk wild
26. by changing any flag Considerations ALTER DS ALTER DS is a sensitive command The asterisk wild card is not supported fro the DS name Changes are immediately visible to all services The DS can be in any state Changing the StartAutomatic attribute does not change the current state of the Omitting a parameter indicates no change to that attribute and does not reset that attribute to its default value Omitting all parameters results in an error The default value for all flags is the current value To set it to on specify the attribute without the OFF option To turn it off specify the OFF option An error while changing one parameter does not stop or roll back changes to other parameters Examples ALTER DS Modify two attributes of the DS TDM_Default_DataSource in all services even though the service SAS is specifically addressed CS gt alter ds as TDM _Default_DataSource MaxServer 10 ConnTimeout no_timeout ALTER DS ODBC AS TDM_Default_DataSource Begun ALTER DS ODBC AS TDM_Default_DataSource Successful for basic settings Turn on trace for all active MXCS servers started by the service as that are using the DS TDM_Default_DataSource CS gt alter ds S as TDM_Default_DataSource Trace ALTER DS ODBC SAS TDM_Default_DataSource Begun ALTER DS ODBC SAS TDM_Default_DataSource Successful for trace Turn off trace fo
27. card is sometimes permitted and directs action on all services The asterisk service name often indicates contact with the MXCS configuration database directly rather than with a specific service in which case the actions still affect all services current or future Use the asterisk if no service is operational yet In this case use commands only on DS and EVAR objects The initial default is one of the existing service or an asterisk if no service is running This component is a process name data type see Fields or Tokens in Commands on page 2 4 ds name is the target DS The initial default is TDM_Default_DataSource This component is an SQL identifier data type see Fields or Tokens in Commands on page 2 4 evar name is the target environment variable with no initial default This component is an SQL identifier data type see Fields or Tokens in Commands on page 2 4 Sserver name is the name of an MXCS server with no initial default This component is a process name data type see Fields or Tokens in Commands on page 2 4 SQL MX Connectivity Service Administrative Command Reference 526350 005 2 6 MXCS Commands and Objects DS Name and EVAR Name groupname is the group login name and must be given if membername is used This component is an SQL identifier data type but is always set to uppercase after the command processes it see Fields or Tokens in Commands on page 2 4 membername
28. is a quoted literal VALUE string is the portion of the object definition that appears after the name It is an SQL string literal and so requires single quotes There is no default See the SQL MX Reference Manual for name and value syntax details MIT number A CTI is the threshold value for the monitored attribute for this resource management policy There is no default This value must be positive and not exceed the maximum value of the LARGEINT SQL data type of 9 223 372 036 854 775 807 Note that the number entered should have no commas and should appear as 9223372036854775807 Commas are inserted only for clarity ON key val is the desired action when the limit is exceeded for this resource management policy The valid values are LOG LOG_WITH_INFO and STOP with LOG also The LOG option is the default Considerations ADD EVAR ADD EVAR is a sensitive command The asterisk wild card is not supported for evar name ADD EVAR fails if you use the same name in an existing EVAR of the same type The new EVAR is added after existing ones of this type If order is important see EVAR Order on page 6 2 All SERVICEs can detect the added EVAR on the DS as soon as it is created but connected servers do not detect it until the current connection is closed You need not stop the DS to execute ADD EVAR Names for some EVARs must be multiword to be unique so blank spaces are permitted in this name with d
29. is the asterisk wild card It then displays only the servers using this DS that were started by the service process specified in obj name Note ds name is an SQL identifier and is therefore case sensitive When using lowercase characters enclose ds name in quotes to preserve the lowercase characters Failure to do so causes ds name to be automatically uppercased during command execution which can cause errors Enter the default ds name as TMD _Default_DataSource SQL MX Connectivity Service Administrative Command Reference 526350 005 4 2 Object Server Commands Considerations INFO SERVER e INFO SERVER is a nonsensitive command e The asterisk wild card is supported All displays are grouped by DS o Output Report INFO SERVER Considerations INFO SERVER The output report contains state values with these definitions STARTING Server initializing starting AVL Server available idle CONING Client connecting CON Client connected DCONING Client disconnecting STOPPING Server Stopping Example INFO SERVER Display attributes cannot be changed with administrative commands These command examples display the attributes of servers owned by SAS The first example does not use the detail option The other examples use the detail option showing an idle server and one connected to a Microsoft Windows client Report without detail option CS gt info server SAS INFO SERVER ODBC SAS
30. it can be in any state Example VERSION SERVICE This example uses an active service and displays NonStop VPROC information for the service SAS and the two libraries showing the subsystem name and build number date CS gt version service SAS VERSION SERVICE ODBC SAS Successful MXCS T7969G10_O1JAN2004_AS_ 1202 CFGCL T7969G10_O1JAN2004_ CFL_1215 MACL T1054G10_01JAN2004_MACL_0129 SQL MX Connectivity Service Administrative Command Reference 526350 005 3 7 Object Service Commands Example VERSION SERVICE This example does not connect to a service or display an MXCS VPROC CS gt version service VERSION SERVICE ODBC Successful MXCS CFGCL T7969G10_O1JAN2004_ CFL_1215 MACL T1054G10_01JAN2004_MACL_0129 SQL MX Connectivity Service Administrative Command Reference 526350 005 3 8 4 Object Server Commands This object is the server to which the remote client connects to access a database and is usually called the MXCS server This object type does not include association servers or configuration servers so the INFO SERVER and STOP SERVER commands cannot administer these servers The association server starts new servers as needed so only the INFO SERVER and STOP SERVER commands are available to manage a server object This section describes the MXCS administrative commands to use for the server object see Valid Command and Object T
31. name in quotes to preserve the lowercase characters Failure to do so causes ds name to be automatically uppercased during command execution which can cause errors Enter the default ds name aS TMD _Default_DataSource Considerations DELETE DS DELETE DS is a sensitive command The asterisk wild card is not supported for the DS name The REASON argument is not required for DELETE DS because it was captured for STOP DS SQL MX Connectivity Service Administrative Command Reference 526350 005 5 14 Object DS Commands Example DELETE DS This example removes the DS Test2 from the system CS gt delete ds SAS Test2 DELETE DS Ol DBC SAS Test2 Successful Example DELETE DS SQL MX Connectivity Service Administrative Command Reference 526350 005 5 15 Object DS Commands INFO DS INFO DS This command displays attributes of one or all defined DSs on this system Command syntax is INFO DS obj name DETAIL ACTIVE obj name system name Sservice name ds name system name is the name of the current system of up to 16 CPUs with the same Expand address and where the target MXCS process is running syst em name and service name identify one service instance service name is the name of the MXCS association server that handles or processes the command or the asterisk wild card An asterisk causes a connection to the database
32. only when that server starts or goes idle Some DS attributes are never passed to the servers For example only the association server uses the maximum number of servers permitted In this configuration two services are running Service A on CPU 5 and Service B on CPU 9 The SQL MX database engine contains the configuration database for the permanent ODBC configuration information DS and EVAR definitions Note that CPU 11 has no MXCS service running on it but it does have a server object Also one instance of MXCI is running on one of the CPUs which is not specified as it does not matter for this discussion On CPU 5 Service A is a logical entity consisting of an association server and a configuration server All three DS definitions are read from the disk and kept current in SQL MX Connectivity Service Administrative Command Reference 526350 005 1 5 MXCS Architecture Overview Complex System Configuration Service A Service A monitors the three MXCS servers it has started in addition to the DS and EVARs they use Each server uses only a few attributes of one DS like time out trace and statistics flags and has all EVARs that belong to that DS defined in its environment Figure 1 2 Complex MXCS Configuration HP NonStop SERVICE A SERVICE B MACL DS1 Library Instance Client DS2 Library Instance DS3 Instance DS1 Instance DS2 Instance DS3 Instance
33. preserve the lowercase characters Failure to do so causes ds name to be automatically uppercased during command execution which can cause errors Enter the default ds name aS TMD Default DataSource COPY old ds name is the name of any existing DS used as a model for the new one on the same system It is an SQL identifier The name must be a DS component name only and not a system or service name All attributes of this existing DS are defaults for the new one Parameters specified on this ADD command override values copied from the existing DS The CpuList values must all come from the command line or from the old DS If you specify one of these numbers on the input specify them all All attributes from the existing DS copy into the new DS creating a clone of the SQL MX Connectivity Service Administrative Command Reference 526350 005 5 2 Object DS Commands ADD DS existing DS The existing DS and the new one must have different names Two DSs with the same name generate an error Using this parameter can be the first step in renaming a DS followed by stopping and deleting the old DS MaxServer count is the upper limit on the servers that can be operational for this service on this DS The default value is 1 A value of 0 gives the system default which is a value determined by the system at run time Valid values are 0 through the total number of ports allowed minus 3 The MXOAS command determines the total number of po
34. rather than a specific service and it is the only valid value when no services are active The state information for one DS instance can be different in each service so a specific service must be selected to get state information When the asterisk is used state information is displayed as n a or not available It cannot be an asterisk when the ACTIVE attribute is specified ds name is the name of the DS to be displayed and can be the asterisk wild card Note ds name is an SQL identifier and is therefore case sensitive When using lower case characters enclose ds name in quotes to preserve the lower case characters Failure to do so causes ds name to be automatically upper cased during command execution which can cause errors Enter the default ds name as TMD_Default_DataSource DETAIL displays all attributes When you omit this option the report provides only the most commonly used attributes When more details are needed this option provides all attributes ACTIVE displays information on only the DSs that are in the starting started or stopping states on one service This flag is valid only when an asterisk is used for the DS name and a specific single service name is specified If no DSs are active on the specified service the command report displays a line stating None SQL MX Connectivity Service Administrative Command Reference 526350 005 5 16 Object DS Commands Considerations I
35. set value PUBLIC_ACCESS_SCHEMA CS gt ADD EVAR MPLOC type set value SDATA03 PERSNL CS gt mode sql gt gt SQL MX Connectivity Service Administrative Command Reference 526350 005 6 5 Object EVAR Commands ALTER EVAR ALTER EVAR This command modifies one existing EVAR in the DS definition specified Command syntax is ALTER EVAR obj name TYPE type name PREFIX string VALUE string or ALTER EVAR obj name TYPE RMP LIMIT number ACTION key val obj name LLL system name Sservice name ds name evar name system name is the name of the current system of up to 16 CPUs with the same Expand address and where the target MXCS process is running syst em name and service name identify one service instance service name is the name of the MXCS association server that handles or processes the command or the asterisk wild card In either case the EVAR is altered on this DS for all servers ds name is the name of the DS owning the EVAR and cannot be the asterisk wild card Note ds name is an SQL identifier and is therefore case sensitive When using lowercase characters enclose ds name in quotes to preserve the lowercase characters Failure to do so causes ds name to be automatically uppercased during command execution which can cause errors Enter the default ds name aS TMD Default DataSource eva
36. this flag Statistics are written to the collector specified when the service is started The default value is OFF when the attribute is not used SessioniInfoStat OFF is a flag to turn ON for this DS the statistics gathering of session statistics at the time a session is terminated Use this flag without the OFF option to turn the individual flag ON This flag can follow the Al1Stat flag to reset only this flag Statistics are written to the collector specified when the service is started The default value is OFF when the attribute is not used ConniInfoStat OFF is a flag to turn ON for this DS the statistics gathering of session statistics at the time a session is established Use this flag without the OFF option to turn the individual flag ON This flag can follow the Al1Stat flag to reset only this flag Statistics are written to the collector specified when the service is started The default value is OFF when the attribute is not used Considerations ADD DS ADD DS is a sensitive command The asterisk wild card is not supported for DS name Parameters are optional and have default values Default value for all flags is ON Specifying the OFF option with the flag is permitted but is unnecessary The OFF option is most useful with ALTER DS and is better omitted with ADD DS Statistics parameters are processed as they occur on the command line For example the Al1lStat flag sets all statistics flags to ON with s
37. 5 2 1 MXCS Commands and Objects MXCS Object Types MXCS Object Types MXCS objects that support the command line interface for SQL MX connectivity service are DS data source A named collection of connection attributes for the servers A DS has a single definition on a particular system and can be seen by all services on the system A particular DS can be different between different systems The DS instance must be in the started state on any service that is using it allowing connections On any other service a specific DS could be in the stopped state EVAR A name and value pair defined in the server environment after the environment client connects to the MXCS server Several different EVAR types exit variable each with slightly different syntax The definition or setting of an EVAR is per each DS System wide settings are not possible Server A process that supports client connections to the database Many MXCS server processes can run on different CPUs within the system each owned by the service the started it Each server also uses one DS However association and configuration servers are not in the MXCS server object class Service A logical object started by the MXOAS command that always contains processes for the association server and usually those for the configuration server also The service object monitors all DSs defined on the system and all user connection requests on the first of several HP NonStop TCP IP por
38. ALTER DS obj name MaxServer count IdleServer count InitServer count IdleTimeout timeout val ConnTimeout timeout val StartAutomatic OFF InitPri priority val Trace OFF CpuList cpu val AllStat OFF SQLExecuteStat OFF SQLExecDirectStat OFF lA r 1 SOLStmtStat OFF SQLFetchStat OFF SQLPrepareStat OFF SessionInfoStat OFF ConnInfoStat OFF obj name system name service name ds name system name is the name of the current system of up to 16 CPUs with the same Expand address and where the target MXCS process is running system name and service name identify one service instance service name is the name of the MXCS association server that handles or processes the command or the asterisk wild card Most changes effect the DS on all services in either case An asterisk causes connection to the database rather than to any specific service and it is the only valid value when no services are active ds name is the name of the DS to be modified and cannot be the asterisk wild card Note ds name is an SQL identifier and is therefore case sensitive When using lowercase characters enclose ds name in quotes to preserve the lowercase characters Failure to do so causes ds name to be automatically uppercased during command execution which can cause errors Enter the default ds name as TMD_Default_DataSource MaxSer
39. CE 3 4 STOP SERVICE 3 5 Considerations STOP SERVICE 3 6 Example STOP SERVICE 3 6 VERSION SERVICE 3 7 Considerations VERSION SERVICE 3 7 Example VERSION SERVICE 3 7 4 Object Server Commands INFO SERVER 4 2 Considerations INFO SERVER 4 3 Output Report INFO SERVER 4 3 Example INFO SERVER 4 3 STOP SERVER 4 5 Considerations STOP SERVER 4 5 Example STOP SERVER 4 6 5 Object DS Commands ADD DS 5 2 Considerations ADD DS 5 6 SQL MX Connectivity Service Administrative Command Reference 526350 005 ii Contents Examples ADD DS 5 7 ALTER DS 5 8 Considerations ALTER DS 5 12 Examples ALTER DS 5 12 DELETE DS 5 14 Considerations DELETE DS 5 14 Example DELETE DS 5 15 INFO DS 5 16 Considerations INFO DS 5 17 Examples INFO DS 5 17 START DS 5 20 Considerations START DS 5 20 Example START DS 5 20 STOP DS 5 21 Considerations STOP DS 5 22 Examples STOP DS 5 22 6 Object EVAR Commands EVAR Types 6 1 EVAR Order 6 2 ADD EVAR 6 3 Considerations ADD EVAR 6 4 Example ADD EVAR 6 4 ALTER EVAR 6 6 Considerations ALTER EVAR 6 7 Example ALTER EVAR 6 8 DELETE EVAR 6 9 Considerations DELETE EVAR 6 10 Example DELETE EVAR 6 10 INFO EVAR 6 11 Considerations INFO EVAR 6 12 Example INFO EVAR 6 12 7 Object User Commands ADD USER 7 2 Considerations ADD USER 7 2 Example ADD
40. Connectivity Service Administrative Command Reference 526350 005 1 9 MXCS Architecture Overview Error Message Overview SQL MX Connectivity Service Administrative Command Reference 526350 005 1 10 2 MXCS Commands and Objects This section describes MXCS Administrative Command Names on page 2 1 MXCS Object Types on page 2 2 Valid Command and Object Type Pairs on page 2 3 Command Rules and General Syntax on page 2 3 Output Report Syntax and Conventions on page 2 9 Security on page 2 10 Example MXCS Configuration on page 2 10 Related Commands on page 2 11 MXCS Administrative Command Names Commands that support administration of SQL MX connectivity service MXCS are ADD Creates and inserts one object into the configuration DELETE Removes one or more objects from the configuration ALTER Modifies one existing object in the configuration INFO Shows attributes and state of one or more objects in the configuration START Makes one or more objects available for use STOP Removes one or more objects from service Server processes are also deleted but services and DSs continue to exist VERSION Displays the product and release IDs date and build number These commands function in pairs with object types but not all combinations of command and object pairs are supported See Valid Command and Object Type Pairs on page 2 3 SQL MX Connectivity Service Administrative Command Reference 526350 00
41. DBC An associated MXCS configuration database allows creation of site specific information to customize the ODBC facility to a specific use or application This guide describes the commands for administrating the ODBC facility and the MXCS configuration database The MXCS administrative commands provide a command line interface that can be scripted to administer the SQL MX ODBC features The commands are packaged in MXCI with SQL MX commands and report writer commands MXCI must be running to access these commands An operating mode within MXCI directs commands to the proper command handlers Note MXCS administrative commands do not administer the JDBC MX product or the SQL MX database itself If MXCS is installed on the system the administrative commands are operational Because MXCS often requires setup before it accesses applications use these commands to configure MXCS initially before it is started and tune the configuration while it is operational Some of the commands are persistent through subsystem shutdown such as ADD DS while others affect only currently running services or servers such as START SERVICE or STOP SERVER MXCS administrative commands use command line format You enter MXCS administrative commands from a keyboard or from a command file after starting MXCI NSM web a Web based GUI administers the same objects that are administered through the command line and MXCS administrative commands However NSM web
42. G TANDEM _ SYSTEM _NSK Sets SCHEMA PUBLIC_ACCESS_SCHEMA Related Commands You can use several related commands outside of the MXCS administrative command library in conjunction with commands supported by the library MXCI Mode Command on page 2 12 Session Variables on page 2 12 MXCI Comment on page 2 12 SQL MX Connectivity Service Administrative Command Reference 526350 005 2 11 MXCS Commands and Objects MXCI Mode Command MXCI Mode Command The MXCI MODE command directs all subsequent commands to the MXCS command library To enter the MXCS mode enter gt gt mode mxcs CS gt To indicate the session is in MXCS mode the prompt changes to cS gt The prompt for continuation lines is the normal gt for all modes The mode prompt of CS persists until the mode is reset Use CS as the prompt for connection services commands To end the MXCS mode enter cs gt mode sql Return to SQL MX mode the default at MXCI start CS gt mode report Go to report writer mode CS gt exit Terminate MXCI To determine the active mode enter CS gt mode display For an example session see Appendix A Example Commands and Objects If there is an SQL transaction in progress and not yet committed the mode switch to mode mxcs s not permitted To enter MXCS administrative commands in this situation start a second instance of MXCI Session Variables Do not use the TACL DEFINE command or OSS shell en
43. H06 26 J06 15 RVU and SQL MX version R3 2 1 IdleTimeout timeout val is a keyword or the integer number of minutes a server waits in the available state for a connection before it stops itself when the count of servers exceeds the IdleServer count value for the DS The default value is SYSTEM_DEFAULT which is defined by MXCS ten minutes currently Other valid values are NO_TIMEOUT and from the integer one to a large number timeout val SYSTEM_DEFAULT NO_TIMEOUT minutes SQL MX Connectivity Service Administrative Command Reference 526350 005 5 3 Object DS Commands ADD DS ConnTimeout timeout val is a keyword or the number of minutes a client server connection can remain idle before the server terminates the connection and becomes available The default value is SYSTEM_DEFAULT which is defined by MXCS ten minutes currently Other valid values are NO_TIMEOUT and from the integer one to a large number timeout val SYSTEM_DEFAULT NO_TIMEOUT minutes StartAutomatic OFF is a flag to request the automatic starting of this DS when its association server process starts Use this flag without the OFF option to turn it ON The default value is OFF when the attribute is not used The DS is created in the stopped state and must be explicitly started on one or more services InitPri priority val is the initial system priority used to start a new server on this DS Valid values are
44. NFO DS The output report contains a column of state values with these definitions STARTING Data source initializing starting first server STARTED Data source started STOPPING Data source stopping all servers not down STOPPED Data source stopped Considerations INFO DS INFO DS is a nonsensitive command The asterisk wild card is valid for service name and ds name but no state information is displayed when service name is an asterisk Most attributes are configured attributes but state and server counts are also shown The operator can change any attributes None of the servers or the EVARs are shown in this display Use INFO on those objects directly if that information is desired Examples INFO DS These commands display the attributes of all DSs on the system This first example has four DSs and is invoked without the detail option CS gt info ds SAS INFO DS ODBC SAS Report Start Server Limits Server Usage Name State Auto Max Init Idle Con Avl Tot TDM_Default_DataSource STARTED ON 5 1 T 0 1 1 DS2 STOPPED OFE 5 3 3 0 0 0 ThisDataSourceNamelIsLongerThan32CharactersButLessThan79Characters STOPPED OFF T 0 0 0 0 0 Mixed Case DSN STARTING OFF 20 7 1 1 1 2 Unused_DS_with_32_Character_Name STOPPED OFE 247 150 7 0 0 0 Cmd Processed 5 objects 0 failed This second example appears with the detail option but was done at a time different than the preceding one Th
45. OFF is a flag to turn ON for this DS the statistics gathering of SQLPrepare statistics at the time a PREPARE statement is received Use this flag without the OFF option to turn the individual flag ON This flag can follow the Al1Stat flag to reset only this flag Statistics are written to the collector specified when the service is started Currently running servers using this DS and started by any service are affected by changing any flag SessioniInfoStat OFF is a flag to turn ON for this DS the statistics gathering of session statistics at the time a session is terminated Use this flag without the OFF option to turn the individual flag ON This flag can follow the Al1Stat flag to reset only this flag Statistics are written to the collector specified when the service is started Currently SQL MX Connectivity Service Administrative Command Reference 526350 005 5 11 Object DS Commands Considerations ALTER DS running servers using this DS and started by any service are affected by changing any flag ConninfoStat OFF is a flag to turn ON for this DS the statistics gathering of session statistics at the time a session is established Use this flag without the OFF option to turn the individual flag ON This flag can follow the Al1Stat flag to reset only this flag Statistics are written to the collector specified when the service is started Currently running servers using this DS and started by any service are affected
46. Objects General MXCS Administrative Command Syntax General MXCS Administrative Command Syntax COMMAND obj type obj name attribute COMMAND is listed in Valid Command and Object Type Pairs on page 2 3 obj type is one of the objects listed in Valid Command and Object Type Pairs on page 2 3 obj name is a string that defines the object to be acted upon with its syntax described in Object Name Components on page 2 5 Object name obj name is optional if the previous command acted on the same object It can also be a subcomponent of the previously addressed object because the library retains the last object name and uses this name to complete the current object name if needed An error occurs if an object name is not provided and there is no default A comma or semicolon delimits an object name attribute is a keyword value pair in the form of keyword value that further specifies the desired action Use either a keyword alone or a keyword followed by a value with a comma or semicolon delimiting an attribute Enclose in single or double quotes values containing a space quote comma or semicolon Keyword can be lowercase uppercase or mixed uppercase and lowercase The value can be an integer key value SQL string literal requires single quotes or an SQL identifier permits double quotes to protect lowercase or special characters To specify several attributes separate each one with a comma Duplicating
47. Port Last State Chg Remot 2Z3505 AVL 0 414 SZTCO 21009 Mar 26 14 07 GL USE TDs ioes eee Saree ene Not Avai Cll App Name sa ced a edi see ars Cl PROC ED sige ve eae be ve e ans a 6 Not Avai Cmd processed 3 objects 0 failed This example stops the DS CS gt stop ds after now reason test complete STOP DS ODBC SAS TEST_DSN Successful This example deletes the D CS gt delete ds DELETE DS ODBC SAS TI CS gt stop service Sas STOP SERVICE CS gt exit End of MXCI Session after now ODBC SAS Successful S stops the service and exits MXCI EST_DSN Successful reason test complete You cannot delete the service through the MXCI interface Delete the service at the TACL prompt by entering stop Sas SQL MX Connectivity Service Administrative Command Reference 526350 005 A 4 Index A ADD command object DS 5 2 object EVAR 6 3 ALTER command object DS 5 8 object EVAR 6 6 Architecture MXCS 1 2 1 3 1 5 1 7 Asterisk wild card using 1 4 Attribute command syntax 2 5 single quotes in 2 8 B Backslash caveat 2 9 C Calls MXCS 1 2 Case sensitivity syntax 2 5 Caveats JDBC MX ODBC MX 1 1 using 1 1 1 7 2 10 2 11 Command syntax fields and tokens 2 4 general format 2 5 Commands 2 11 caveats 2 9 list of 2 1 MXCI mode 2 11 object pairing 2 3 objects description 2 2 output reports 2 9 Command line terminating c
48. S CAE sie ge eoe ed Fee De OFF SOLEXECDLTECES bas wc acts eea pie ats ON SOLSEMES CAG o ere eels Sead ee erate Scenes OFF SQLPEE CHS CAG ene e a EEN E EEE sees ON CS gt info server INFO SERVER ODBC AS Report DS Name TDM _Default_DataSource PName State SPid TCP IP PN Port Last State Chg Remote System Nam S Z3471 AVL 1 375 SZTCO 21002 Mar 26 13 49 DS Name EST_DSN PName State SPid TCP IP PN Port Last State Chg Remote System Nam SQL MX Connectivity Service Administrative Command Reference 526350 005 A 3 Example Commands and Objects System Nam Not Avail System Nam Not Avail System Nam Not Avail Z3503 AVL 0 388 ZTCO 21007 Mar 26 14 07 Z3504 AVL 1 381 SZTCO 21008 Mar 26 14 07 Z3505 AVL 0 414 SZTCO 21009 Mar 26 14 07 Cmd processed 4 objects 0 failed CS gt info server detail ds Test_DSN INFO SERVER ODBC SAS Report DETAIL DS Name TEST_DSN PName State SPid TCP IP PN Port Last State Chg Remot 2Z3503 AVL 0 388 ZTCO 21007 Mar 26 14 07 Cl User LD cheb ee Payee Not Avai Cl App Names gar ei ees shes CI POE ED sb Baie d hale He esters Not Avai DS Name TEST_DSN PName State SPid TCP IP PN Port Last State Chg Remot Z3504 AVL 1 381 SZTCO 21008 Mar 26 14 07 Gl USE DD i665 sia Siesta 6 aie ante ens Not Avail Cl App Nansena aee a elke ena ELAR LOC ED oi sees haus Side oe Not Avail DS Name TEST_DSN PName State SPid TCP IP PN
49. SAGE Warning messages resulting from command entry syntax error SUBSYSTEM Messages translated from client library codes LOWLAYER 1 Messages from layers below the client library LOWLAYER 2 Additional messages from layers below the client library In the SQL MX Messages Manual notation for an MXCS administrative command error message often contains substitution variables similar to this example 15206 SUBSYSTEM Bad return code inti library call functions name failed Substitution variables appearing as inti are integers and those appearing as string1 are strings Some cases use a more meaningful variable such as functions name but substitution variables are always shown in italic SQL MX Connectivity Service Administrative Command Reference 526350 005 1 8 MXCS Architecture Overview Error Message Overview Some error messages also suggest recovery action as shown in this example of error 15215 FRROR 15215 SUBSYSTEM SERVICE name used cannot supply this info library call CFGGetStatusService failed SUGG SERVICE name was probably and should be a specific SERVICE name When a recovery suggestion is given it follows the error description and is introduced by the string SUGG Suggested recovery action is a best effort analysis of the problem indicated Under certain circumstances recovery might not always succeed SQL MX
50. SQL MX Connectivity Service Administrative Command Reference Abstract This manual describes the ODBC administrative commands running in the HP NonStop SQL MX Connectivity Service MXCS environment and accessed through the SQL MX conversational interface MXCl These commands support manipulation of the logical objects that define the user visible attributes of the SQL MX connectivity service MXCS Product Version MXCS ACL 1 1 APB Supported Release Version Updates RVUs This manual supports J06 03 and all subsequent J series RVUs H06 03 and all subsequent H series RVUs and G06 23 ABA and all subsequent G series RVUs until otherwise indicated by its replacement publications Part Number Published 526350 005 July 2013 Document History Part Number Product Version Published 526350 001 MXCS ACL 1 0 April 2004 526350 002 MXCS ACL 1 1 ABA August 2004 526350 003 MXCS ACL 1 1 ABO March 2005 526350 004 MXCS ACL 1 1 APB February 2013 526350 005 MXCS ACL 1 1 APB July 2013 Legal Notices Copyright 2013 Hewlett Packard Development Company L P Confidential computer software Valid license from HP required for possession use or copying Consistent with FAR 12 211 and 12 212 Commercial Computer Software Computer Software Documentation and Technical Data for Commercial Items are licensed to the U S Government under vendor s standard commercial license The information contained herein is subject to change with
51. SZTCO 21001 Mar 26 13 37 CFG This example creates the DS and uses options that are not optimal for normal use For example its CpuList option limits the servers to running on CPU 0 and 1 It also starts statistic recording that can reduce performance fill the logs and disable idle server and idle connection timeouts After starting the servers they are persistent and do not end You can configure the DS without starting a service by using an asterisk for the service name which connects it directly to the database Regardless of how the DS is created all existing services immediately see the DS This DS is created in the stopped state CS gt add ds Test_DSN MaxServer 5 IdleServer 3 InitServer 2 IdleTimeout gt NO_TIMEOUT ConnTimeout NO_TIMEOUT InitPri 140 CpuList 0O 1 gt SQLExecDirectStat SQLFetchStat SQLPrepareStat ADD DS ODBC SAS TEST_DSN Successful This example adds EVARs to the DS definition CS gt add evar ESTIMATED COST type rmp limit 500 action stop ADD EVAR ODBC SAS TEST_DSN ESTIMATED COST Successful CS gt add evar timeout value reset ADD EVAR ODBC SAS TEST_DSN TIMEOUT Successful This command produces an error because of a misspelled EVAR name CS gt add evar sratch_disks value S data0l S data02 ODBC data03 ADD EVAR ODBC SAS TEST_DSN SRATCH DISKS Failed ERROR 15408 Lower layers failed to perform actio
52. USER 7 2 ALTER USER 7 3 Considerations ALTER USER 7 3 Example ALTER USER 7 3 6 Object EVAR Commands SQL MX Connectivity Service Administrative Command Reference 526350 005 Contents A Example Commands and Objects DELETE USER 7 4 Considerations DELETE USER 7 4 Example DELETE USER 7 4 INFO USER 7 5 Considerations INFO USER 7 5 A _ Example Commands and Objects index Figures Figure 1 1 MXCSArchitecture 1 3 Figure 1 2 Complex MXCS Configuration 1 6 Figure 2 1 MXCS Object Relations 2 3 SQL MX Connectivity Service Administrative Command Reference 526350 005 iv What s New in This Manual Manual Information Abstract This manual describes the ODBC administrative commands running in the HP NonStop SQL MX Connectivity Service MXCS environment and accessed through the SQL MX conversational interface MXCI These commands support manipulation of the logical objects that define the user visible attributes of the SQL MX connectivity service MXCS Product Version MXCS ACL 1 1 APB Supported Release Version Updates RVUs This manual supports J06 03 and all subsequent J series RVUs H06 03 and all subsequent H series RVUs and G06 23 ABA and all subsequent G series RVUs until otherwise indicated by its replacement publications Part Number Published 526350 005 July 2013 Docume
53. USER is a sensitive command The asterisk wild card is not supported Only the user SUPER SUPER can use this command SUPER SUPER and DEFAULT users cannot be deleted Example DELETE USER This example removes the named user from database permissions CS gt delete user grouptst george DELETE USER ODBC GROUPTST GEORGE Successful SQL MX Connectivity Service Administrative Command Reference 526350 005 7 4 Object User Commands INFO USER INFO USER This command displays user names and permissions to the MXCS configuration database access list It allows display of permissions for one user all users in one group or all users with permissions defined Command syntax is INFO USER obj name obj name system name groupname membername system name is the name of a group of up to 16 CPUs with the same Expand address system name and service name identify one instance groupname is the NonStop OS group logon name membername is the NonStop OS user logon name with no aliases permitted Considerations INFO USER e INFO USER is not a sensitive command Can be used by anyone to display which users have Oper permissions to the MXCS configuration database groupname can be the asterisk wild card only when membername is also the wild card Example INFO USER This example first displays the named user s database permissions and then all users with perm
54. and the default prefix all No default prefix control CONTROL QUERY DEFAULT define ADD DEFINE rmp Not applicable set SET SQL MX Connectivity Service Administrative Command Reference 526350 005 6 1 Object EVAR Commands EVAR Order EVAR Order Use the INFO EVAR command to determine the order in which the environment variables are applied when used EVARS appear in the order of their creation or addition with the latest EVAR added for a specific type at the end of the list If the order of the EVARs is important individually delete one or more of the existing target EVARS by using the DELETE EVAR command Add them back individually by using the ADD EVAR command in the order that you want them to appear SQL MX Connectivity Service Administrative Command Reference 526350 005 6 2 Object EVAR Commands ADD EVAR ADD EVAR This command adds one EVAR to the DS definition specified Command syntax is ADD EVAR obj name TYPE type name PREFIX string VALUE string or ADD EVAR obj name TYPE RMP LIMIT number ACTION key val obj name LLL system name Sservice name ds name evar name system name is the name of the current system of up to 16 CPUs with the same Expand address and where the target MXCS process is running syst em name and service name identify one service instance service name is the name of the MXCS association server that handles or processes th
55. c This documentation and the software to which it relates are derived in part from materials supplied by the following 1987 1988 1989 Carnegie Mellon University 1989 1990 1991 Digital Equipment Corporation 1985 1988 1989 1990 Encore Computer Corporation 1988 Free Software Foundation Inc 1987 1988 1989 1990 1991 Hewlett Packard Company 1985 1987 1988 1989 1990 1991 1992 International Business Machines Corporation 1988 1989 Massachusetts Institute of Technology 1988 1989 1990 Mentat Inc 1988 Microsoft Corporation 1987 1988 1989 1990 1991 1992 SecureWare Inc 1990 1991 Siemens Nixdorf Informationssysteme AG 1986 1989 1996 1997 Sun Microsystems Inc 1989 1990 1991 Transarc Corporation This software and documentation are based in part on the Fourth Berkeley Software Distribution under license from The Regents of the University of California OSF acknowledges the following individuals and institutions for their role in its development Kenneth C R C Arnold Gregory S Couch Conrad C Huang Ed James Symmetric Computer Systems Robert Elz 1980 1981 1982 1983 1985 1986 1987 1988 1989 Regents of the University of California Printed in the US SQL MX Connectivity Service Administrative Command Reference What s New in This Manual Manual Information v New and Changed Information v About This Manual vii Audience vii Related Doc
56. d Processed 2 objects 0 failed SQL MX Connectivity Service Administrative Command Reference 526350 005 5 22 6 Object EVAR Commands This section describes the MXCS administrative commands to use for the object EVAR see Valid Command and Object Type Pairs on page 2 3 EVAR Types on page 6 1 EVAR Order on page 6 2 ADD EVAR on page 6 3 ALTER EVAR on page 6 6 DELETE EVAR on page 6 9 INFO EVAR on page 6 11 EVAR Types The EVAR object defines NonStop OS or SQL environment variables and provides commands to manage them The server environment uses these variables to define various aspects of queries usually substitution variables or SQL operational parameters These variables affect operations after the client has connected to the MXCS server An EVAR has three main components type name and value Each DS has its own collection of EVARs EVARs are not shared among DSs In these examples of different types of EVARs the uppercase text example is displayed by the INFO command and is stored in the database after the input command is parsed and defaults added Note Single quotes delimiting OFF are required CONTROL QUERY DEFAULT QUERY_CACHE STATISTICS OFF control type example ADD DEFINE KEVIN_TABLE FILE DATA0O2 KEVIN2 KTABLE define typ xample SET NAMETYPE ANSI set typ xampl This list indicates the supported types
57. d card AFTER stop_mode specifies the termination time of the MXCS server with a key value NOW terminates the server abruptly abort as fast as possible A client connected to the server receives the communication link failure error on the next action that accesses the server The client is required to either disconnect and connect to another server or to quit Incomplete transactions are rolled back This is the default mode Considerations STOP SERVER STOP SERVER is a sensitive command STOP SERVER deletes the server from the system The server does not transition to a stopped state and wait for a start command after STOP SERVER e The asterisk wild card is not supported The service that starts the MXCS server owns it and stops it SQL MX Connectivity Service Administrative Command Reference 526350 005 4 5 Object Server Commands Example STOP SERVER Stopping a DS stops all servers it owns on the specified SERVICE Stopping a service stops all servers it owns Client connections can change rapidly Issue INFO SERVER DETAIL before issuing STOP server to verify that the server is connected to the appropriate client e lf the target server does not exist STOP SERVER returns an error If no client is connected to the target server it terminates immediately e lf the server is already in the stopping state STOP SERVER returns only a success message e To start and stop DS trace and statistics attr
58. displayed When the value for InitServer count is greater than 0 the servers are started in blocks of five with a check for incoming connection requests occurring between each block To permit servicing incoming users the DS goes to the STARTED state as soon as the first server starts These servers count as idle servers if they are not allocated to new users immediately Note The value of 1000 is applicable from H06 26 J06 15 RVU and SQL MX version R3 2 1 TdleTimeout timeout val is a keyword or integer number of minutes a server waist in the available state for a connection before it stops itself when the count of servers exceeds the DS server count for the DS Valid values are SYSTEM_DEFAULT which is defined by MXCS ten minutes currently NO_TIMEOUT and the integer one to a large number ConnTimeout timeout val is a keyword or the integer number of minutes a client server connection remains idle before the server terminates the connection and becomes available Valid values are SYSTEM_DEFAULT which is defined by MXCS ten minutes currently NO_TIMEOUT and the integer one to a large number StartAutomatic OFF is a flag to request the automatic starting of this DS when its associated server process starts Use this flag without the OFF option to turn it ON The default value is OFF when the attribute is not used The DS is created in the stopped state and must be explicitly started on one or more services SQL
59. does not support command files and it must first be installed on the system This section describes Features and Functionality on page 1 1 Architecture Overview on page 1 2 User Interface With MXCI on page 1 4 General Features on page 1 4 Software Installation on page 1 5 Complex System Configuration on page 1 5 Error Message Overview on page 1 7 Features and Functionality e Administers ODBC MXCS in NonStop SQL MX Release 2 0 ABA and later releases e Provides a scriptable command line interface through MXCI on an HP NonStop operating system OS e Reports if a command fails to supply requested information SQL MX Connectivity Service Administrative Command Reference 526350 005 1 1 MXCS Architecture Overview Architecture Overview Configures a new installation of MXCS or modifies an existing installation e Accesses objects only on the system where MXCI is running Provides database security so that all users can view objects but only specified users can modify them e Displays attributes and states of the objects within the ODBC MXCS configuration e Displays and manages the ODBC MXCS configuration as five separate object types Service the MXOAS command starts each service Server Data source DS Environment variable EVAR for each DS user for permissions User for permissions Supports administrative commands INFO ADD DELETE START STOP ALTER VERSION
60. e command or the asterisk wild card In either case the EVAR is added to this DS on all servers ds name is the name of the DS owning the EVAR and cannot be the asterisk wild card Note ds name is an SQL identifier and is therefore case sensitive When using lowercase characters enclose ds name in quotes to preserve the lowercase characters Failure to do so causes ds name to be automatically uppercased during command execution which can cause errors Enter the default ds name aS TMD Default DataSource evar name is the name of the EVAR to be added and cannot be the asterisk wild card It is an SQL identifier and so requires double quotes in some cases When the type is a define the name can optionally contain a leading equal sign with or without quotes The name is always set to uppercase even when enclosed in quotes TYPE type name is one of the valid types in the table under EVAR Types on page 6 1 The type all is not valid for this command The default type is control SQL MX Connectivity Service Administrative Command Reference 526350 005 6 3 Object EVAR Commands Considerations ADD EVAR PREFIX string is the portion of the object definition that appears before the name It is an SQL string literal and so requires single quotes The default value is determined by the type See EVAR Types on page 6 1 For consistency this value is displayed in uppercase letters even though it
61. e Overview User Interface With MXCl User Interface With MXCl The MXCI interface with MXCS administrative commands is similar to its interface for the report writer or SQL command handlers The basic features are MXCS commands terminate with a semicolon with command input occurring only after the semicolon is entered Enclose embedded semicolons in single or double quotation marks If the MXCS mode is set the prompt changes from gt gt to cs gt for terminal users but not for log file or non tty input streams After you set the MXCS mode all commands go to MACL until you either reset the mode or enter exit In MXCS mode basic SQL commands generate syntax errors MXCI manages batch input files and output log files as usual but now these files can contain MXCS commands preceded by the mode command MXCI passes a break event to MACL for handling If a command is in progress MACL stops generating report and error messages No support exists for critical section or rollback events for MACL commands These commands immediately complete When a command initiates change in the MXCS environment a break event arrival could interrupt the process To determine if a break event is successful check state information for the object in the current command If an outstanding transaction exists attempts to switch to the MXCS mode in MXCl fail with an error message For example executing queries with autocommit set to off default is on
62. e a CPU can be down now and up later nonexistent CPU numbers are not reported when set but return an EMS warning when you attempt to use them This option affects only new servers currently running servers are not changed The CpuList values come from either the command line or from the source DS and not a combination of the two If you specify one of these CPUs on the command line you must specify them all cpu val ALL nbrO nbri nbri5 AllStat OFF is a flag to set for this DS all seven individual statistics gathering flags for servers started by this service Use this flag without the OFF option to turn all seven individual flags ON This flag must precede other individual statistics flags which reset just those individual flags Currently running servers started by any service are affected by changing this flag SQL MX Connectivity Service Administrative Command Reference 526350 005 5 10 Object DS Commands ALTER DS SOQLExecuteStat OFF is a flag to turn ON for this DS the statistics gathering of SQLExecute statistics at the time an EXECUTE statement is received for servers started by this service Use this flag without the OFF option to turn the individual flag ON This flag can follow the Al1Stat flag to reset just this one flag Statistics are written to the collector specified when the service is started Currently running servers started by any service are affected by changing this flag SQLExecDi
63. e and DS Because servers are not connected to clients yet all servers are in shown the AVL state and all connected client information is listed as Not Avail in the displays CS gt info service detail INFO SERVICE ODBC SAS Report PName State SPid TCP IP PN Port Last Updated Type SAS AVL 1 386 SZTCO 21000 Mar 26 13 49 AS Z3445 AVL 1 394 SZTCO 21001 Mar 26 13 37 CFG DS Name active only DS State SVE Con Avl Tot TDM_Default_DataSource STARTED 0 al 1 EST_DSN STARTED 0 3 3 Totals For Service 0 4 4 CS gt info ds detail INFO DS ODBC SAS TEST_DSN Report detailed Name ODBC SAS TEST_DSN CpuList 0 1 INECPE E a e a o ae a a 140 CurrentStatess oe e eee et STARTED ConnectedServersS enai a ranas 0 AvailableServers 2 23 Last SCaAteChg iiio eea a Mar 26 14 07 LAS CUP CACC a eres eats s aeaa Mar 26 13 39 TALES SL VC brenia tetera bi bare ate ws Soa erate eo eis ele 3 IdleTimeouts eea eesti os ae NO_TIMEOU MAX S SEV Ton sia 8 ore EE SNS SRE eS naw Se 5 COMNT IMEOUCs an aeea see des eee NO_TIMEOU TRLESELV CS Bie oes Beets e E WS aed SO olen 2 StartAutomatiC eesi eects eai tend where ee OFF METAS Cid Metals ar e tence E ds tot AEREE E Bia tere fei OFF SOLPTEPALTSS TAD Kis ie eet ete ee tone we Whee we laine ON COnMINEOSCAD SS saae a aie i E audited OFF SQLExecuteStat 0 200s OFF SESSTONINEO
64. e hours or days for the client to disconnect normally This is the default mode REASON text is anonempty SQL string literal of up to 70 characters which indicates why the DS is being shut down It is written to the EMS log by the service if the command is accepted Strings of 70 or more characters are truncated with a warning Single quoting is required Considerations STOP DS e STOP DS is a sensitive command The asterisk wild card is valid for service name or ds name but not both in the same command Check on the progress of the STOP DS command by using the INFO DS command Issuing STOP DS inhibits new client access to the target DS lf target DS is already stopped or stopping STOP DS returns a success message e Target DS must be stopped in all services before deleting it using DELETE DS Examples STOP DS This example stops the DS TDM_Default_DataSource being used by the service SAS and also stops all servers started by the service As that are using this DS CS gt stop ds SAS TDM Default_DataSource REASON text text STOP DS ODBC SAS TDM_Default_DataSource Successful this example stops all DSs used by the service SAs along with all MXCS servers CS gt stop ds SAS after now reason Shutdown for the day STOP DS ODBC SAS Begun STOP DS ODBC SAS TDM_Default_DataSource Successful STOP DS ODBC SAS Test2 Successful Cm
65. errors for a particular event you must be able to recognize all error report formats Some error reports contain several error events so it can be useful to group errors by event Note that the initial message for an event contains no keyword after the error number A single error message for one error event looks like CS gt info ds abc option INFO DS ODBC SASM ABC Failed ERROR 15242 Command has an invalid attribute OPTION SUGG Check spelling or use of extra commas A usage error message for one error event looks like CS gt info xx abc EBRROR 15453 Unknown object type XX x x WARNING 15288 USAGE INFO command supports object types DS EVAR SERVER SERVICE USER SQL MX Connectivity Service Administrative Command Reference 526350 005 1 7 MXCS Architecture Overview Error Message Overview A multiple error message for one error event looks like CS gt start ds catalog_ds START DS ODBC SASM CATALOG_DS Failed ERROR 15380 DS not found ODBC ASM CATALOG_DS ERROR 15309 SUBSYSTEM DS not found library call CFGStartDS failed x x BRROR 15202 LOWLAYER 1 Data source does not exist These examples show actual error reports See the SQL MX Messages Manual for explanations of each message number such as 15380 15309 15202 and so forth In some cases error messages from lower layers appear redundant as the preceding example
66. ervice Administrative Command Reference 526350 005 xii About This Manual Notation for Messages Nonitalic text Nonitalic letters numbers and punctuation indicate text that is displayed or returned exactly as shown For example Backup Up lowercase italic letters Lowercase italic letters indicate variable items whose values are displayed or returned For example p register process name Brackets Brackets enclose items that are sometimes but not always displayed For example Event number number Subject first subject value A group of items enclosed in brackets is a list of all possible items that can be displayed of which one or none might actually be displayed The items in the list can be arranged either vertically with aligned brackets on each side of the list or horizontally enclosed in a pair of brackets and separated by vertical lines For example proc name trapped in SQL in SQL file system Braces A group of items enclosed in braces is a list of all possible items that can be displayed of which one is actually displayed The items in the list can be arranged either vertically with aligned braces on each side of the list or horizontally enclosed in a pair of braces and separated by vertical lines For example obj type obj name state changed to state caused by Object Operator Service process name State changed from old objstate to objstate Operator Req
67. es you to specify the name of a command file For start up information see MXCI Mode Command on page 2 12 For examples see Example Commands and Objects on page A 1 Complex System Configuration This subsection describes a complex MXCS configuration on one system showing the objects that MXCS administrative commands manage service server DS and EVAR In Figure 1 2 on page 1 6 a system is shown with three of its CPUs represented and MXCS objects distributed across these CPUs The service object is a logical entity consisting of two processes one or more DS instances a table of all servers it has started and owns and memory resident copies of EVARS owned by each DS instance Data sources exist in three places in three forms e A copy on the disk that has no state except existence or not e A copy in the service the DS instance that has a state stopped is default state A partial copy kept in each server The configuration server in each service reads all DS instances at service start up and keeps them current However states for DS instances can be different in different services The association server starts each server and passes its DS attributes at server start up and also when certain attributes change However when an EVAR for a DS instance is added deleted or changes value it is not passed to connected servers because this action changes the environment during transactions EVARs pass from a DS instance to a server
68. haracter 2 3 Comment syntax MXCI 2 12 D DELETE command object DS 5 13 object EVAR 6 9 Dollar sign caveat 2 9 DS instance definition 2 2 DS name case and quotation marks 2 7 object syntax 2 6 DS definition 2 2 E Environment variables EVAR object 6 1 Error report 1 7 1 9 EVAR components 6 1 name object syntax 2 6 order of variables 6 2 Exiting MXCS mode 1 4 F Fields and tokens command syntax 2 4 G Groupname object syntax 2 7 INFO command command syntax 3 2 object DS 5 14 object EVAR 6 11 object SERVER 4 2 object SERVICE 3 2 Installing MXCS administrative commands 1 5 Interface MXCI 1 4 SQL MX Connectivity Service Administrative Command Reference 526350 005 Index 1 Index L Leaving MXCS mode 1 4 Messages error 1 7 1 9 Mode command 2 12 MXCI comment syntax 2 12 mode command 2 11 MXCS architecture 1 2 1 3 display prompt 1 4 feature and functions 1 1 MXCI interface 1 4 starting MXCS 2 12 MXCS exit mode 1 4 O Object DS ADD command 5 2 DS ALTER command 5 8 DS DELETE command 5 13 DS INFO command 5 14 DS START command 5 18 DS STOP command 5 19 EVAR ADD command 6 3 EVAR ALTER command 6 6 EVAR DELETE command 6 9 EVAR INFO command 6 11 SERVER INFO command 4 2 SERVER STOP command 4 5 SERVICE INFO command 3 2 SERVICE START command 3 4 SERVICE STOP command 3 5 SERVICE VERSION command 3 7 Object name command syntax 2 5 double quotes 2 8 Object syntax
69. he initial port number PN 15000 the trace detail level E 0 and the port range PR 250 MXOAS name AS nowait term Szhome TCP ZTCO PN 15000 E 0 PR 250 When SQL MxX is initialized the TDM_Default_DataSource is created with these defaults MaxServer 5 IdleServer 1 InitServer J IdleTimeout SYSTEM_DEFAUL ConnTimeout SYSTEM_DEFAUL StartAutomatic OFF lt No Resource Statistics gt lt No Resource Management Policy EVARs gt lt No Control EVARs gt lt No Define EVARs gt lt No Set EVARs gt A sample configuration of a new DS normally entered for testing is Data source name TDM_Default_DataSource MaxServer 20 IdleServer 5 InitServer 10 IdleTimeout SYSTEM DEFAULT ConnTimeout 60 minutes StartAutomatic Manual Trace Off SQOLStmtStat On SQLPrepareStat On SQLExecuteStat On SOLExecDirectStat On SQLFetchStat On ConninfoStat On SessionInfoStat On RM Estimated Cost STOP_LOG_WITH_ERROR Define EMPLOYEE CLASS MAP FILE DATA0O1 PERSNL EMPLOYEE Define DEPT CLASS MAP FI SDATA02 PERSNL DEPT Control QUERY DEFAULT HIST_NO_STATS_ROWCOUNT 123456789 Control QUERY DEFAULT HIST_NO_STATS_UEC 99 Control TABLE TIMEOUT 3000 Control TABLE PERSNL JOB MDA OFF Sets CATALO
70. ibutes for all servers owned by a DS use the ALTER DS command Example STOP SERVER This example stops the server Z0123 owned by SAs CS gt STOP SERVER SAS z0123 STOP SERVER ODBC SAS Z0123 Successful SQL MX Connectivity Service Administrative Command Reference 526350 005 4 6 5 Object DS Commands This object is a server side data source DS that represents a named collection of use connection and database attributes Clients specify the desired DS at connection time to establish the run time environment The DS is a permanent object that is recorded in the MXCS administrative database The DS is owned by each service that is using it The same DS has the same configured values in each service using it but it can have different states trace states and server counts All services see all DSs on a system and changes to configured values of the DS are propagated to all services You can start a DS instance in some services and stop it in others Before you can view DSs on a service you must start the service once You can view DSs in the MXCS administrative database without starting a service This section describes the MXCS administrative commands that are available for the DS object see Valid Command and Object Type Pairs on page 2 3 e ADD DS on page 5 2 ALTER DS on page 5 8 DELETE DS on page 5 14 INFO DS on page 5 16 START DS on page 5 20 SQL MX Connectivity Service Administrative Command Refere
71. ically Other attribute changes require terminating the service and starting it again with new options by using the TACL command STOP and RUN MXOAS The association server process must be running but service can be in any state SQL MX Connectivity Service Administrative Command Reference 526350 005 3 2 Object Service Commands Output Report States INFO SERVICE Output Report States INFO SERVICE The INFO SERVICE report contains state values with these definitions STARTI AVL STOPPI STOPPE NG NG Service is initializing starting Service is available Service is going to STOP state but some DS not yet stopped Service is running but not accepting users Examples INFO SERVICE These examples display the attributes of the service AS e Without DETAIL option CS gt info service AS INFO SERVICE ODBC AS Report PName State SPid TCP IP PN Port Last Updated Type SAS AVL 1 387 SZTCO 21000 Jan 22 12 15 AS 2Z1094 AVL Loi SZTCO 21001 Jan 22 12 15 CFG With DETAIL option CS gt info service SAS detail INFO SERVICE ODBC SAS Report with details PName State SPid TCP IP PN Port Last Updated Type SAS AVL 1 387 SZTCO 21000 Jan 22 12 15 AS 2Z1094 AVL 1 377 SZTCO 21001 Jan 22 12 15 CFG DS Name active only DS State Svr Con Avl Tot Test2 STARTED 0 1 dt TDM_Default_DataSource STARTED 9 2 11 Totals For Service 9 3 12
72. inated SQL execute direct statistics gathered when an EXECUTEDIRECT statement is received SQL statement statistics gathered when a PREPARE statement is received SQL fetch statistics when closing a statement SQL MX Connectivity Service Administrative Command Reference 526350 005 5 19 Object DS Commands START DS START DS This command starts one DS on one service or on all services if the asterisk wild card is specified New clients can then use this DS If the DS is already started START DS returns a success message Command syntax is START DS obj name obj name system name Sservice name ds name system name is the name of the current system of up to 16 CPUs with the same Expand address and where the target MXCS process is running syst em name and service name identify one service instance service name is the name of the MXCS association server that handles or processes the command where this DS should be started Using the asterisk wild card indicates to start all services which enables the DS to be started in all services for one system on one command ds name is the name of the DS to be started and cannot be the asterisk wild card Note ds name is an SQL identifier and is therefore case sensitive When using lowercase characters enclose ds name in quotes to preserve the lowercase characters Failure to do so causes ds name to be automaticall
73. indicates to stop all services and is valid only when a specific DS is selected This value allows the DS to be stopped on all services on one system in one command so a subsequent delete is possible ds name is the name of the DS to be stopped It can be the asterisk wild card provided a specific service is selected Note ds name is an SQL identifier and is therefore case sensitive When using lowercase characters enclose ds name in quotes to preserve the lowercase characters Failure to do so causes ds name to be automatically uppercased during command execution which can cause errors Enter the default ds name aS TMD Default DataSource AFTER stop_mode specifies the termination time of the server with one of these key values NOW terminates the server abruptly abort as fast as possible A client connected to the server receives the communication link failure error on the next action that accesses the server The client is expected to either disconnect and connect to another server or to quit Incomplete transactions are rolled back SQL MX Connectivity Service Administrative Command Reference 526350 005 5 21 Object DS Commands Considerations STOP DS YU ISCONNECT terminates the server but not until the remote client terminates the connection The client connected to a server is not notified that a termination is requested and continues working until it disconnects normally It could tak
74. is example has two DSs CS gt INFO DS SAS detail active INFO DS ODBC SAS Report detailed Name ODBC SAS TDM Default_DataSource CpuList 0 1 2 3 4 DTPA PAE Lee eck cecal eah ee ald aide gel E Ge codon aa 140 CUPLENT SEAT Sie ere ea ion oA deel 6 STARTED ConnectedServers 22 200 1 AvailableServers 00 oil LastStateChg Feb 14 10 08 TASTUPCATC Cnc eke kw n aE E 8 ec ie ae Not Set TALES SEV SL 5 6 oe ose Roe ee ee a Rhee en EAN 1 IdleTimeout SYSTEM_DEFAUL MaxSeryer es bo00end oie eels LG ews 5 COnn Timeout ss ves ees See 4 SYSTEM_DEFAUL TNA SSL VS cee dee terete Mie ce teste e We ers 1 SCALCAUPOMAEL Circ siecle end wees ee ON DAC Siac ed aren e eaa a dake EE ee OFF SOLPLEPArSS EAE 5 sree vow eeraa de erase aS OFF ConnInfoOStats wes ea s E ae sk whe OFF SQOLEXSCUUESSE Abi esse ee sei etde ace a e ee OFF S ssLonIntoStat s r ewe 6 bee ee OFF SQLExecDirectStat 6 OFF SOLS CMOS Cet Aa w wh aes Se we aoe wae OFF SOLBeEECHS ta ia sede end atacand A E Sue wd ee OFF SQL MX Connectivity Service Administrative Command Reference 526350 005 5 17 Object DS Commands Examples INFO DS Name ODBC AS Mixed Case DSN CpuList 3 4 5 12 13 14 15 MICP E unig Gasca orate ool te deihie S 4 150 CUBLENCSCALCE aie soe ae eae Saye STARTING ConnectedServers 22000 1 AvailableServers 222 06
75. is part of the SQL MX library of manuals which includes Introductory Guides SQL MX Comparison Guide for SQL MP Users SQL MX Quick Start Reference Manuals SQL MX Reference Manual DataLoader MX Reference Manual SQL MX Messages Manual SQL MX Glossary Describes SQL differences between SQL MP and SQL MX Describes basic techniques for using SQL in the SQL MX conversational interface MXCIl Includes information about installing the sample database Describes the syntax of SQL MX statements MXCI commands functions and other SQL MX language elements Describes the features and functions of the DataLoader MX product a tool to load SQL MX databases Describes SQL MX messages Defines SQL MX terminology SQL MX Connectivity Service Administrative Command Reference 526350 005 vii About This Manual Programming Manuals SQL MX Programming Manual for C and COBOL SQL MX Programming Manual for Java Specialized Guides SQL MX Installation and Management Guide SQL MX Query Guide SQL MX Data Mining Guide SQL MX Queuing and Publish Subscribe Services SQL MX Report Writer Guide SQL MX Connectivity Service Manual SQL MX Guide to Stored Procedures in Java Online Help Related Documentation Describes how to embed SQL MX statements in ANSI C and COBOL programs Describes how to embed SQL MX statements in Java programs according to the SQLJ standard Describes how to plan for install c
76. issions CS gt info user grouptst george INFO USER ODBC GROUPTST GEORGE Report GROUPTST GEORGE Oper gt CS gt info user INFO USER ODBC Report P23 4S O18 Ooi oo Oe Loans a ua ara gers tate Ate a ed AIDS cage Sasa O aa 9 iol athena aa a a Aaa PUBLIC Fou marnani mada User SUPER SUPER Oper GROUPTST SUSAN Oper GROUPTST TOM Oper GROUPTST GEORGE User GROUPTST MARY Oper SQL MX Connectivity Service Administrative Command Reference 526350 005 7 5 Object User Commands Considerations INFO USER SQL MX Connectivity Service Administrative Command Reference 526350 005 7 6 A Example Commands and Objects The appendix provides examples to Start an MXCS ODBC service named ASs Create and start a DS named TEST_DSN Review the resulting MXCS configuration Stop and delete the DS Stop the service e Delete the service Because example object names are not case sensitive they appear in lowercase However they appear in uppercase in reports To protect the case of a DS name enclose it in double quotes Service names are automatically translated to uppercase Commands in these examples use the defaulting feature for component names where component names are retained from previous commands These MXCI commands appear in the order that they appear in this example mode mxcs info service Sas add ds Test_DSN add evar ESTIMATED COST add evar timeout
77. jects SQL MX Connectivity Service Administrative Command Reference 526350 005 3 1 Object Service Commands INFO SERVICE INFO SERVICE This command displays the name and attributes of the service object including state information DS summary and user connection information The name of the service is always the name of the ODBC association server process defined by the RUN MXOAS command Command syntax is INFO SERVICE obj name DETAIL obj name system name Sservice name system name is the name of the current system of up to 16 CPUs with the same Expand address and where the target MXCS process is running syst em name and service name identify one service instance service name is the name of the MXCS association server process of the service to be displayed and must be an association server When the asterisk wild card is used each association server on the system is contacted DETAIL displays all attributes If you omit this option the report provides only the most commonly used attributes Considerations INFO SERVICE e INFO SERVICE is a nonsensitive command e The asterisk wild card is supported but supplies information about services only on the local system e Processes that represent the service object are the association server and the configuration server for each service supported You can change only the state of the service object dynam
78. l likely fail because z0123 is probably not an association server process ID When the final component of the name is defaulted while other components are specified use trailing dot period separators to show missing components This guideline does not apply to missing leading components For example this string addresses the named service on the same system as before no leading period is needed INFO SERVICE SAR SQL MX Connectivity Service Administrative Command Reference 526350 005 2 7 MXCS Commands and Objects Command Size Limit But the period is required in this command because the DS name is defaulted INFO DS SAR2 This last example uses the DS named in the previous command but specifies a different service it assumes a previous command acted on a DS The example shows how to get state information on one specific DS from each service When an intermediate component is specified by a default you must specify its terminating period For example this command specifies the EVAR on Sas2 owned by the same DS named in the previous example INFO EVAR Sas2 Evar2 Command Size Limit Commands have no size limit so you can continue long statements or commands over multiple lines breaking them at any space character A semicolon terminates a statement or command you break over several lines To break a line within SQL identifier or string literal use the CONCAT operator and quote the two
79. me Expand address system name and service name identify one instance groupname is the NonStop OS group logon name membername is the NonStop OS user logon name with no aliases permitted PERM perm val is the permission value of Oper Operator or User assigned to the named user The permission keyword Operator is equivalent to Oper and is the default Considerations ADD USER e ADD USER is a sensitive command The asterisk wild card is not supported Only the user SUPER SUPER or an alias can use this command To change the permission of users already assigned a permission use the ALTER USER command ADD USER command terminates with an error if the user is already defined Example ADD USER This example adds the named user and gives database permissions to execute any command CS gt add user grouptst george perm oper ADD USER ODBC GROUPTST GEORGE Successful SQL MX Connectivity Service Administrative Command Reference 526350 005 7 2 Object User Commands ALTER USER ALTER USER This command changes one user s permission in the MXCS configuration database access list Command syntax is ALTER USER obj name PERM perm val obj name system name groupname membername system name is the name of a group of up to 16 CPUs with the same Expand address system name and service name identify one instance groupname is the NonStop OS group logon name
80. n be down now and up later nonexistent CPU numbers return an EMS warning only when you attempt to use them Only new servers are affected not currently running servers The CpuList values come from either the command line or from the source DS but not a combination of the two If you specify one of these CPUs on the command line you must specify them all cpu val ALL nbrO nbri nbri5 AllStat OFF is a flag to set for this DS all seven individual statistics gathering flags Use this option without the OFF option to turn these flags ON Use this flag along with the copy option to reset all flags regardless of the flags an existing DS has set for statistics This flag must precede other individual statistic flags which reset just those individual flags The default value is OFF when the attribute or copy is not used SOLExecuteStat OFF is a flag to turn ON for this DS the statistics gathering of SQLExecute statistics at the time an EXECUTE statement is received Use this flag without the OFF option to turn the individual flag ON This flag can follow the Al1Stat flag to reset just this one flag Statistics are written to the collector specified when the service is started The default value is OFF when the attribute is not used SQLExecDirectStat OFF is a flag to turn ON for this DS the statistics gathering of SQLExecDirect statistics at the time an EXECUTE statement is received Use this flag withou
81. n requested ERROR 15310 SUBSYSTEM SQL error from LowLayer library call CFGSetEnvironmentValues failed ERROR 15202 LOWLAYER 1 ERROR 2050 SRATCH_DISKS is not the name of any DEFAULTS table attribute ERROR 8822 Unable to prepare the statement These examples complete adding EVARs and displaying the results CS gt add evar scratch_disks value Sdata0l data02 ODBC data03 ADD EVAR ODBC SAS TEST_DSN SCRATCH_DISKS Successful CS gt add evar EMP type define value CLASS MAP FILE SDATA0Q1 PERSNL EMPLOYEE ADD EVAR ODBC SAS TEST_DSN EMP Successful CS gt info ds detail INFO DS ODBC SAS TEST_DSN Report detailed Name ODBC SAS TEST_DSN CpuList 0 1 TiC PRE seat ot a vote kaahs ese igo ae eicarese 140 CUBKENTS LACS sisteitec Gielen lek E E A STOPPED ConnectedServers ee eee eee eee ee 0 AvailableServers 0 LastStateChg Dec 31 18 00 LASCTUPAACS seua teea eis Mar 26 13 39 LOLCSErV OR none eeN amp tee we SE ee ew 3 ratermett a stew dead weld NO_TIMEOU M xServye oye eka OES Oe OE Sow AWS EW we 5 CONN TAMe Out eg aie ia oa ee ee NO_TIMEOU TAS SRV GL as ss suas la ee eos BGs Side ees ees ene a s 2 StaABEAUCOMAt Les aiaa tel ere etre aud Sided OFF PEACE Sa estes Bestel sees bs as phe aE Bic el shh TANE oe OFF SOLPREPALS STALE wre eels Bots wine decane eas wos ON
82. nce 526350 005 5 1 Object DS Commands ADD DS ADD DS This command adds one DS to the MXCS configuration on the system Command syntax is ADD DS obj name COPY old ds name MaxServer count IdleServer count InitServer count IdleTimeout timeout val ConnTimeout timeout val StartAutomatic OFF InitPri priority val Trace OFF CpuList cpu val AllStat OFF SQLExecuteStat OFF SQLExecDirectStat OFF SOLStmtStat OFF SQLFetchStat OFF SQLPrepareStat OFF SessionInfoStat OFF ConniInfoStat OFF NNN NNN obj name system name Sservice name ds name system name is the name of the current system of up to 16 CPUs with the same Expand address and where the target MXCS process is running syst em name and service name identify one service instance service name is the name of the MXCS association server that handles or processes the command or the asterisk wild card The new DS is added to all services in either case An asterisk causes connection to the database rather than to any specific service and it is the only valid value when no services are active ds name is the name of the DS to be added created and cannot be the asterisk wild card It must be a new name or the command will fail Note ds name is an SQL identifier and is therefore case sensitive When using lowercase characters enclose ds name in quotes to
83. no commas and should appear as 9223372036854775807 Commas are inserted only for clarity ION key val is the desired action when the limit is exceeded for this resource management policy The valid values are LOG LOG_WITH_INFO and STOP with LOG also The LOG option is the default Considerations ALTER EVAR ALTER EVAR is a sensitive command The asterisk wild card is not supported for evar name The order of the EVARs is not changed Use the INFO EVAR to determine the order in which the environment variables can be applied when used ALTER EVAR changes the first EVAR it finds with a prefix and name match It then scans for additional matches and displays warnings because subsequent names can be used at run time instead of the first name ALTER EVAR rebuilds the object from the data provided in the command Syntax and use of this command are similar to the ADD EVAR command But unlike ADD EVAR which places the new EVAR at the end of the list ALTER EVAR replaces the object where it originally appeared in the list Names for some EVARs must be multiword to be unique so blank spaces are permitted in this name with double quotes The resulting definition consists of the prefix name and value fields concatenated together in that order The existing values for PREFIX LIMIT and ACTION become the defaults but VALUE does not default SQL MX Connectivity Service Administrative Command Reference 526350 005 6 7 Objec
84. nt History Part Number Product Version Published 526350 001 MXCS ACL 1 0 April 2004 526350 002 MXCS ACL 1 1 ABA August 2004 526350 003 MXCS ACL 1 1 ABO March 2005 526350 004 MXCS ACL 1 1 APB February 2013 526350 005 MXCS ACL 1 1 APB July 2013 New and Changed Information Updated the initserver count inthe ADD DS and ALTER DS section SQL MX Connectivity Service Administrative Command Reference 526350 005 v What s New in This Manual New and Changed Information SQL MX Connectivity Service Administrative Command Reference 526350 005 vi About This Manual This manual describes the administrative commands available to administer ODBC in an SQL MX connectivity service MXCS running on a single HP NonStop system These commands are implemented internally as the SQL MX administrative command library MACL are linked into the SQL MX command interface MXCl and support manipulation of logical objects defining the user visible attributes of the ODBC facility of SQL MX Connectivity Service MXCS Audience This manual is intended for database administrators and programmers who Manage the ODBC facility of MXCS for connectivity to the NonStop SQL MX Use the MXCS administrative commands on the MXCI command line rather than through the Web based NSM web product e Use batch files to change or add to the MXCS configuration Commands in this manual run at the MXCI prompt Related Documentation This manual
85. onfiguration server are not terminated but they recognize only administrative commands lf the service is already in the stopped or stopping state STOP SERVICE is successful but has no effect Example STOP SERVICE This example stops the service AS CS gt stop service SAS after now reason text STOP SERVICE ODBC S AS Successful SQL MX Connectivity Service Administrative Command Reference 526350 005 3 6 Object Service Commands VERSION SERVICE VERSION SERVICE This command returns version information for these components The MXCS association server The Client library The MACL This information helps when reporting problems Command syntax is VERSION SERVICE obj name obj name system name Sservice name system name is the name of the current system of up to 16 CPUs with the same Expand address and where the target MXCS process is running syst em name and service name identify one service instance service name is the name of the MXCS association server process for the target service When the asterisk wild card is used the report will not contain a version for the MXCS process Considerations VERSION SERVICE VERSION SERVICE is a nonsensitive command When an asterisk is used no service is contacted so version information for MXCS is not reported When an asterisk is not used the named service must be running but
86. or having an open BEGIN WORK transaction causes failures MACL supports no variable expansion in its input commands General Features Asterisk is the only wild card supported in command names but only for specific commands No patterns are supported Wild card xyz or a b Causes an error The asterisk wild card applies only to objects on the specific system supporting the MXCI process See Command Rules and General Syntax on page 2 3 Object name defaulting is supported to reduce typing The most recent object named of each type persists until it is changed Commonly used commands for the EVAR object have defaults to reduce typing See Default Object Name on page 2 7 Each DS EVAR and user is checked for uniqueness A duplicate causes failure of the ADD command ALTER or DELETE commands act on the first match they detect and generate a warning about the successive duplicates The INFO command displays duplicate objects but does not issue a warning SQL MX Connectivity Service Administrative Command Reference 526350 005 1 4 MXCS Architecture Overview Software Installation Error messages describe the problem and where possible suggest a recovery action Software Installation MXCS administrative commands are installed as part of MXCI No special installation process is needed to install software for these commands Starting Leaving and Ending MXCI The MXCI command has many options One of them enabl
87. ouble quotes The resulting definition consists of the prefix name and value fields concatenated together in that order Example ADD EVAR This example adds an EVAR of type define with the name GROUP to the DS ab DM Default_DataSource You can use the equal sign in the name but it is not SQL MX Connectivity Service Administrative Command Reference 526350 005 6 4 Object EVAR Commands Example ADD EVAR required Use of the specific service ASs is not significant here the asterisk wild card is less ambiguous CS gt add evar SAS TDM_Default_DataSource GROUP type define value CLASS MAP FILE SDATA3 PERSNL GROUP ADD EVAR ODBC TDM Default_DataSource GROUP Successful This example adds an EVAR type rmp and displays it The EVAR is named ESTIMATED COST in uppercase and enclosed in double quotes to protect the space character Entering the name in lowercase is permitted but all characters are automatically converted to uppercase In this example the service name and data source name are defaulted to those used in the preceding example CS gt add evar ESTIMATED COST type rmp limit 5000 action log_with_info ADD EVAR ODBC SAS TDM_DEFAULT_DATASOURCE ESTIMATED COST Successful CS gt info evar type rmp INFO EVAR ODBC SAS TDM_DEFAULT_DATASOURCE Report Resource Management Policies ESTIMATED COST Limit 5000 Action LOG_WITH_INFO
88. out notice The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services Nothing herein should be construed as constituting an additional warranty HP shall not be liable for technical or editorial errors or omissions contained herein Export of the information contained in this publication may require authorization from the U S Department of Commerce Microsoft Windows and Windows NT are U S registered trademarks of Microsoft Corporation Intel Itanium Pentium and Celeron are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries Java is a registered trademark of Oracle and or its affiliates Motif OSF 1 UNIX X Open and the X device are registered trademarks and IT DialTone and The Open Group are trademarks of The Open Group in the U S and other countries Open Software Foundation OSF the OSF logo OSF 1 OSF Motif and Motif are trademarks of the Open Software Foundation Inc OSF MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THE OSF MATERIAL PROVIDED HEREIN INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE OSF shall not be liable for errors contained herein or for incidental consequential damages in connection with the furnishing performance or use of this material 1990 1991 1992 1993 Open Software Foundation In
89. ppercase or lowercase alphanumeric characters A through Z or a through Z plus O through 9 SQL identifier Single word uppercase or lowercase unless within optional double quotes and used for object types DS and EVAR components With double quotes the character set expands to include spaces tabs punctuation and lowercase alphabetic letters See the Identifiers topic in the SQL MX Reference Manual for an explanation of SQL identifiers Unlike with a true SQL identifier MXCS administrative commands accept regular identifiers containing special characters in unquoted strings except token separators Errors for leading or trailing space characters in a name are reported SQL string literal Requires single quotes is single or multiword is case sensitive unless noted otherwise in the specific command permits all printable characters and is used only for attribute values See the Literals topic in the SQL MX Reference Manual for an explanation of SQL string literals Unlike a true SQL string literal MXCS administrative commands do not accept the optional leading character set identifier and the empty string literal But these fields accept leading and trailing space in the string Generally only these SQL types can be enclosed in quotes or split across multiple lines Splitting requires quotes and the CONCAT operator SQL MX Connectivity Service Administrative Command Reference 526350 005 2 4 MXCS Commands and
90. r name is the name of the EVAR to be altered and cannot be the asterisk wild card It is an SQL identifier and so requires double quotes in some cases When the type is a define the name can optionally contain a leading equal sign with or without quote The name is always set to uppercase even when enclosed in quotes TYPE type name is one of the valid types from the table in EVAR Types on page 6 1 The type all is not valid for this command The default type is control SQL MX Connectivity Service Administrative Command Reference 526350 005 6 6 Object EVAR Commands Considerations ALTER EVAR PREFIX string is the portion of the object definition that appears before the name It is an SQL string literal and so requires single quotes The default value is determined by the type See EVAR Types on page 6 1 For consistency this value is stored in uppercase letters even though it is a quoted literal VALUE string is the portion of the object definition that appears after the name It is an SQL string literal and so requires single quotes There is no default See the SQL MX Reference Manual for name and value syntax details LIMIT number ACT is the threshold value for the monitored attribute for this resource management policy There is no default This value must be positive and not exceed the maximum value of the LARGEINT SQL data type of 9 223 372 036 854 775 807 The number entered should have
91. r all active MXCS servers started by any service that is using DS TDM_Default_DataSource and also modify other parameters Because failures do not roll back or stop the actions this output shows the progress of changes to the DS attributes in the database and the trace results on each active service In this example the DS name TDM_Default_DataSource is enclosed in quotes to SQL MX Connectivity Service Administrative Command Reference 526350 005 5 12 Object DS Commands Examples ALTER DS preserve its lowercase characters If quotes are not used the DS name automatically changes to uppercase TDM_Default_DataSource when the command executes CS gt alter ds 7 purist SL A i ITER DS D ER DS ER DS ER DS ER DS ER DS ER DS ER DS ER DS A A AL Ae AL A A A Cc md a O O O O O O O O O listat DBC DBC DBC DBC DBC DBC DBC DBC DBC TDM TDM_ TDM TDM TDM_ SAS1 SAS2 SAS3 SAS4 DM_Default_DataSource Trace off maxserver 6 initpri 52 Default_DataSource Begun Default_DataSource Successfu Default_DataSource Successfu Default_DataSource Successful for InitPri Default_DataSource Successful for statistics DM_Default_DataSource Failed for trace DM _Default_DataSource Successful for trace DM_Default_DataSource Failed for t
92. race for basic settings for CpuList r 1 1 1 DM Default_DataSource Failed for trace processed 4 objects 3 failed Iteration stopped after 3 failures SQL MX Connectivity Service Administrative Command Reference 526350 005 5 13 Object DS Commands DELETE DS DELETE DS This command removes one DS from the MXCS configuration on the target system The DS must be in the stopped state in all services on the system or an error is generated and the DS is not deleted Command syntax is DELETE DS obj name obj name Ll system name Sservice name ds name system name is the name of the current system of up to 16 CPUs with the same Expand address and where the target MXCS process is running syst em name and service name identify one service instance service name is the name of the MXCS association server that handles or processes the command or the asterisk wild card In either case the DS must be in the stopped state on all services and is deleted from all services The asterisk indicates to connect to the database rather than to a specific service and it is the only valid value when no services are active ds name is the name of the DS to be deleted It cannot be the asterisk wild card or the default DS TDM_Default_DataSource Note ds name is an SQL identifier and is therefore case sensitive When using lowercase characters enclose ds
93. reate and manage an SQL MX database Explains how to use installation and management commands and utilities Describes how to understand query execution plans and write optimal queries for an SQL MX database Describes the SQL MX data structures and operations to carry out the knowledge discovery process Describes how SQL MxX integrates transactional queuing and publish subscribe services into its database infrastructure Describes how to produce formatted reports using data from a NonStop SQL MX database Describes how to install and manage the SQL MX Connectivity Service MXCS which enables applications developed for the Microsoft Open Database Connectivity ODBC application programming interface API and other connectivity APIs to use SQL MX Describes how to use stored procedures that are written in Java within SQL MX The SQL MX Online Help consists of Reference Help Messages Help Glossary Help NSMWeb Help Visual Query Planner Help Overview and reference entries from the SQL MX Reference Manual Individual messages grouped by source from the SQL MX Messages Manual Terms and definitions from the SQL MX Glossary Context sensitive help topics that describe how to use the NSM web management tool Context sensitive help topics that describe how to use the Visual Query Planner graphical user interface SQL MX Connectivity Service Administrative Command Reference 526350 005 viii About This
94. rectStat OFF is a flag to turn ON for this DS the statistics gathering of SQLExecDirect statistics at the time an EXECUTE statement is received for servers started by this service Use this flag without the OFF option to turn the individual flag ON This flag can follow the Al1Stat flag to reset only this flag Statistics are written to the collector specified when the service is started Currently running servers started by any service are affected by changing this flag SOoLStmtStat OFF is a flag to turn ON for this DS the statistics gathering of statement statistics at the time a PREPARE statement is received for servers started by this service Use this flag without the OFF option to turn the individual flag ON This flag can follow the AllStat flag to reset only this flag Statistics are written to the collector specified when the service is started Currently running servers started by this service are affected by changing this flag SQLFetchStat OFF is a flag to turn ON for this DS the statistics gathering of SQLFetch statistics at the time a statement is closed for servers started by this service Use this flag without the OFF option to turn the individual flag ON This flag can follow the AllStat flag to reset only this flag Statistics are written to the collector specified when the service is started Currently running servers using this DS and started by any service are affected by changing any flag SQLPrepareStat
95. rts allowed Different services can have different limits which prevents you from validating them when you create them IdleServer count is the lower limit on the available idle servers that are operational for this service on this DS Valid values are 0 through MaxServer count with 0 as the default This count represents idle servers that are waiting for user connections At DS startup once the InitServer count is satisfied additional servers are started until the IdleServer count is reached Initially idle servers are started in blocks of five with a check for incoming connection requests occurring between each block After peak user loads idle servers are terminated to the IdleServer count value see IdleTimeout on this page InitServer count is the suggested number of servers that each service starts when the DS first starts Legal values are from 0 to the smaller of either 1000 or the value specified by the MaxServer count with the default value as 0 If the initial server count exceeds 1000 an error is displayed When the value for InitServer count is greater than 0 the servers are started in blocks of five with a check for incoming connection requests occurring between each block To permit servicing incoming users the DS goes to the STARTED state as soon as the first server starts These servers count as idle if they are not allocated to new users immediately Note The value of 1000 is applicable from
96. s the name of the DS owning the EVAR and cannot be the asterisk wild card Note ds name is an SQL identifier and is therefore case sensitive When using lowercase characters enclose ds name in quotes to preserve the lowercase characters Failure to do so causes ds name to be automatically uppercased during command execution which can cause errors Enter the default ds name aS TMD Default DataSource evar name is the name of the EVAR to be deleted and can be the asterisk wild card If the EVAR name is an asterisk and the type is a11 all EVARs under that DS are deleted If the EVAR name is an asterisk and a type other than a11 is specified EVARs of that type are deleted from the DS If the EVAR name is not an asterisk the type cannot be a11 and only that EVAR is deleted The EVAR name is an SQL identifier and requires double quotes in some cases When the type is a define the name can optionally contain a leading equal sign with or without quotes The name is always set to uppercase even when enclosed in quotes TYPE type name is one of the valid types in the table under EVAR Types on page 6 1 SQL MX Connectivity Service Administrative Command Reference 526350 005 6 9 Object EVAR Commands Considerations DELETE EVAR DELETE EVAR is a sensitive command Considerations DELETE EVAR The asterisk wild card is supported for evar name DELETE EVAR deletes the first EVAR it find
97. s with a name match and then scans for additional matches and displays warnings if found All SERVICEs remove this deleted EVAR as soon as it is removed from the database but connected servers do not remove it until the current connection is closed You need not stop the DS to execute DELETE EVAR Example DELETE EVAR This example deletes an EVAR of type define with the name GROUP from the DS TDM required CS gt delete evar TDM_Default DELETE EVAR ODBC TDM Default Default_DataSource You can use the equal sign in the name but it is not _DataSource GROUP type define _DataSource GROUP Successful SQL MX Connectivity Service Administrative Command Reference 526350 005 6 10 Object EVAR Commands INFO EVAR INFO EVAR This command displays the named EVAR from the DS definition specified Command syntax is INFO EVAR obj name TYPE type name obj name Ll system name Sservice name ds name evar name system name is the name of the current system of up to 16 CPUs with the same Expand address and where the target MXCS process is running syst em name and service name identify one service instance service name is the name of the MXCS association server that handles or processes the command or the asterisk wild card ds name is the name of the DS owning the EVAR and cannot be the asterisk wild card
98. shows Note that the first line starts with a pair of hyphens and is a result summary not an error message This first line of the message gives the basic action the full object name and summary status as success or failure Most commands using a wild card can produce multiple error events from one command For example if you request information on all DS objects and the system is busy it is possible the command will fail for several or even all the DS objects it iterates over Such iterative commands often stop after the fourth error event A command with a wild card can quickly exceed the ten message limit for error reports with the tenth message stating that some messages were dropped Each MXCS administrative command error message starts with three asterisks followed by ERROR or WARNING and the error message number Warnings are informational and do not stop command processing Errors usually stop command processing on the object where the error occurred However some commands can continue processing additional objects if the asterisk wild card is specified When more than one error is reported for an event the first message is the primary message describing the error and possible recovery Subsequent messages result from internal calls to subsystems and often provide more details about the problem Although primary error messages have no leading keyword subsequent messages can contain one of these keywords U
99. so run on any specified CPU when you manually start services from a TACL prompt by using the MXOAS command No MXCS administrative command is available to launch a service The START SERVICE command requires that the MXOAS command has already started the processes and as such only moves the service from stopped to started and allows users to start connecting Also the STOP SERVICE command does not kill the service process It merely prevents establishment of new connections and terminates existing connections and the servers supporting them Error Message Overview MXCS administrative command error messages for any single event consist of one or more lines of error messages limit of ten displayed in this general format Note A message with content as shown in the first line of this example is always displayed Successive lines containing additional details are frequently displayed CS gt command Error 1l5nnn Primary error message numbered 15200 to 15499 stating reason for failure of the MXCS command Error 15nnn KEYWORD Detailed error info from client library or usage information Keyword is SUBSYSTEM or USAGE Error 15nnn LOWLAYER 1 Report of problems from layers below client library Error 1l5nnn LOWLAYER n Additional report from layers below client library where n is 2 3 4 and so forth indicating the sequential number of the message up to 8 To easily locate all
100. substrings with the same single or double quote character Using space characters around the CONCAT operator is optional but is recommended for readability In this example an EVAR name with a long DS name in it is broken Make a break within a quoted string not at the period after it add evar This is a long DS name that will be broken into two not three parts ThisEvarName Type set value 34567 Single Quotes for Attribute Values Using single quotes around attribute values is optional except when an SQL string literal is required That is extra quotes around attribute values do not cause a syntax error Extra quotes on keywords do cause an error The MXCS administrative command parser removes unneeded single or double quotes before the strings are used It also adds single quotes if they are required by the MXCS subsystem or database Double Quotes for Object Names Using double quotes around object names those that are SQL identifiers is optional except when there are nonalphanumeric characters spaces or lowercase characters in the name Extra double quotes around identifiers that do not require them do not cause a syntax error but do inhibit automatically translating lowercase characters to uppercase The command parser removes the quotes before using the name internally Empty Quoted Strings Empty quoted strings are reported as syntax errors SQL MX Connectivity Service Administrative Command Reference
101. t EVAR Commands Example ALTER EVAR Omitting all parameters causes an error e All SERVICEs can detect this changed EVAR as soon as it is updated on the disk but connected servers do not detect it until the current connection is closed You need not stop the DS to execute ALTER EVAR Example ALTER EVAR This example modifies an EVAR of type define with the name GROUP in the DS TDM_Default_DataSource You can use the equal sign in the name but it is not required CS gt alter evar TDM_Default_DataSource GROUP type define value CLASS MAP FILE S DATA55 PERSNL GROUP ALTER EVAR ODBC TDM_Default_DataSource GROUP Successful SQL MX Connectivity Service Administrative Command Reference 526350 005 6 8 Object EVAR Commands DELETE EVAR DELETE EVAR This command removes the named EVAR from the specified DS definition Command syntax is DELETE EVAR obj name TYPE type name obj name Ll system name Sservice name ds name evar name system name is the name of the current system of up to 16 CPUs with the same Expand address and where the target MXCS process is running syst em name and service name identify one service instance service name is the name of the MXCS association server that handles or processes the command or the asterisk wild card In either case the EVAR is deleted on this DS for all servers ds name i
102. t MXCI to the MXCS mode as described in MXCI Mode Command on page 2 12 Figure 1 1 MXCS Architecture User Command Command Response Configuration MXCI Server Error Strings d Report SQL MX Writer y Commands Commands Association Configuration Server SQL MX Client Library Engine MXCS Client MXCS i Server VST002 vsd An operational MXCS association server is not required for data source and environmental variable configuration commands but must exit stopped state is OK when you want to query the current status of the service data source or servers running in that service In Figure 1 1 assume that the MXCS facility is started The normal flow for MXCS administrative command processing is 1 MXCI starts and accepts a command from a terminal or disk file 2 The MXCI command manager has been set to the MXCS mode so it passes the command to the MACL routines MACL parses the command and requests the client library perform the action 4 The client library transmits requests to the appropriate MXCS component and returns responses 5 MACL formats the responses into reports MACL returns status to the MXCI command manager The MXCI command manager displays all result and error lines and then waits for further input SQL MX Connectivity Service Administrative Command Reference 526350 005 1 3 MXCS Architectur
103. t the OFF option to turn the individual flag ON This flag can follow the Al1Stat flag to reset only this flag Statistics are written to the collector specified when the service is started The default value is OFF when the attribute is not used SOLStmtStat OFF is a flag to turn ON for this DS the statistics gathering of statement statistics at the time a PREPARE statement is received Use this flag without the OFF option to turn the individual flag ON This flag can follow the Al1Stat flag to reset only this flag Statistics are written to the collector specified when the service is started The default value is OFF when the attribute is not used SQLFetchStat OFF is a flag to turn ON for this DS the statistics gathering of SQLFetch statistics at the time a statement is closed Use this flag without the OFF option to turn the individual flag ON This flag can follow the Al1Stat flag to reset only this flag SQL MX Connectivity Service Administrative Command Reference 526350 005 5 5 Object DS Commands Considerations ADD DS Statistics are written to the collector specified when the service is started The default value is OFF when the attribute is not used SQLPrepareStat OFF is a flag to turn ON for this DS the statistics gathering of SQLPrepare statistics at the time a PREPARE statement is received Use this flag without the OFF option to turn the individual flag ON This flag can follow the Al1Stat flag to reset only
104. ted The association server can be in any state but it must exist after invoking the TACL command RUN MXOAS The service can be in the stopped state because it is configured to enter it at startup or because an operator previously issued STOP If this service is already in the available state START SERVICE is successful but has no effect Example START SERVICE This example starts the service SAS CS gt start service SAS START SERVICE ODBC SAS Successful SQL MX Connectivity Service Administrative Command Reference 526350 005 3 4 Object Service Commands STOP SERVICE STOP SERVICE This command which executes the controlled shutdown of the service e Puts the service object in the stopping state but does not terminate the association server process Stops all DSs and therefore all servers on the target service Actual termination of the server occurs at different times depending on the stop mode attribute you specify Command syntax is STOP SERVICE obj name AFTER stop mode REASON text obj name system name Sservice name system name is the name of the current system of up to 16 CPUs with the same Expand address and where the target MXCS process is running system name and service name identify one service instance service name is the name of the MXCS association server process of the service to be stopped AFTER stop mode specifies ho
105. theses commas semicolons and other symbols not previously described must be typed as shown For example error NEXTFILENAME file name LISTOPENS SU Sprocess name su name Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown For example repetition constant list Item Spacing Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma For example CALL STEPMOM process id If there is no space between two items spaces are not permitted In this example no spaces are permitted between the period and any other items Sprocess name su name Line Spacing If the syntax of a command is too long to fit on a single line each continuation line is indented three spaces and is separated from the preceding line by a blank line This spacing distinguishes items in a continuation line from items in a vertical list of selections For example ALTER OUT file spec LINE attribute spec Notation for Messages This list summarizes the notation conventions for the presentation of displayed messages in this manual Bold Text Bold text in an example indicates user input typed at the terminal For example ENTER RUN CODE 27123 CODE RECEIVED 123 00 The user must press the Return key after typing the input SQL MX Connectivity S
106. ts assigned to it by the MXOAS command User A logical object that defines access permissions for an administrator of the MXCS configuration database Object Ownership Hierarchy A DS is anamed collection of attributes that resides on a disk A DS instance is a logical entity in a service that has all attributes of the DS plus a state A DS instance also owns all the servers started by the service that uses it Figure 2 1 A server uses one DS and its EVARS and is owned by one service One DS owns each defined environment variable Each EVAR is an attribute of one DS Each service has a DS instance and several services can use a DS at the same time Object Ownership Complexity Complexity appears when the system has several services and DSs as shown in Figure 2 1 The DS resides on a disk as a set of values and attributes with the memory resident DS instance built in each service from the DS definition on that disk When the DS is added altered or deleted all services are notified of the changes and each DS instance is updated EVAR changes are also propagated to all services but only to idle servers Servers with existing connections are not modified Two DSs can have an EVAR of the same name but each EVAR is unique with its own values SQL MX Connectivity Service Administrative Command Reference 526350 005 2 2 MXCS Commands and Objects Valid Command and Object Type Pairs Figure 2 1 MXCS Object Relations DS Instance
107. ts contains the command and full object name This line can be the only line that some commands display In addition to the first line some commands display a line for each object accessed as shown in the preceding example while others display multiple lines per object If you use a wild card in a command and no objects are found the word None appears When a specific object is requested by name and not found an error message appears Reports that display many objects resulting from commands with wild cards provide a count of objects output as the last line The last line indicates how many errors if any were encountered during object iteration In general iterations do not stop on one error unless that error stops processing on other objects SQL MX Connectivity Service Administrative Command Reference 526350 005 2 9 MXCS Commands and Objects Security Security MACL has two classes of commands Informational commands which return data Any user can issue these commands INFO VERSION Sensitive commands which change states and values and add or delete objects Only a user with operator permissions can issue these commands ADD ALTER DELETE START STOP Users issuing sensitive commands are validated against the list of user objects defined in the MXCS configuration database Each user object has either operator or user permissions Each system has its own set of user object definitions just as it has its own
108. uccessive commands on the same command line setting individual flags to OFF Services see the DS as soon as it is created After creation the DS has no EVARs defined unless the COPY parameter creates them The DS is created in the stopped state and must be explicitly started on one or more services Specifying the StartAutomatic attribute starts the target DS when its associated server process starts Except for errors when setting the trace flag during an ADD command an error causes the DS to be removed completely SQL MX Connectivity Service Administrative Command Reference 526350 005 5 6 Object DS Commands Examples ADD DS Examples ADD DS This example creates the DS Mixed Case DSN inall services even though the service SAS is specifically addressed CS gt add ds SAS Mixed Case DSN MaxServer 30 IdleServer 5 InitServer 10 IdleTimeout SYSTEM_DEFAULT ConnTimeout 60 AllStat ADD DS ODBC SAS Mixed Case DSN Successful Use this command to clone a DS and change one parameter CS gt add ds S SAS Son of Mixed Case DSN COPY Mixed Case DSN MaxServer 50 ADD DS ODBC AS Son of Mixed Case DSN Successful SQL MX Connectivity Service Administrative Command Reference 526350 005 5 7 Object DS Commands ALTER DS ALTER DS This command is similar to the ADD DS command except ALTER DS modifies the attributes of an existing DS in the MXCS configuration on one system Command syntax is
109. uest Unknown Vertical Line A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces For example Transfer status OK Failed Percent Sign A percent sign precedes a number that is not in decimal notation The notation precedes an octal number The B notation precedes a binary number The H notation precedes a hexadecimal number For example 6005400 B101111 SH2E Sp register H e register SQL MX Connectivity Service Administrative Command Reference 526350 005 xiii About This Manual Change Bar Notation Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version Change bars are vertical rules placed in the right margin of changed portions of text figures tables examples and so on Change bars highlight new or revised information For example The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run Time Environment CRE The CRE has many new message types and some new message type codes for old message types In the CRE the message type SYSTEM includes all messages except LOGICAL CLOSE and LOGICAL OPEN SQL MX Connectivity Service Administrative Command Reference 526350 005 xiv E MXCS Architecture Overview The NonStop SQL MX connectivity service MXCS includes support for remote connections to the SQL MX database such as ODBC and J
110. umentation vii Notation Conventions x 1 MXCS Architecture Overview Features and Functionality 1 1 Architecture Overview 1 2 User Interface With MXCI 1 4 General Features 1 4 Software Installation 1 5 Starting Leaving and Ending MXCI 1 5 Complex System Configuration 1 5 Error Message Overview 1 7 2 MXCS Commands and Objects MXCS Administrative Command Names 2 1 MXCS Object Types 2 2 Object Ownership Hierarchy 2 2 Object Ownership Complexity 2 2 Valid Command and Object Type Pairs 2 3 Command Rules and General Syntax 2 3 Command Termination 2 3 Fields or Tokens in Commands 2 4 General MXCS Administrative Command Syntax 2 5 Command Syntax Case 2 5 Object Name Components 2 5 DS Name and EVAR Name 2 7 Default Object Name 2 7 Hewlett Packard Company 526350 005 i Contents 3 Object Service Commands Command Size Limit 2 8 Single Quotes for Attribute Values 2 8 Double Quotes for Object Names 2 8 Empty Quoted Strings 2 8 Command Caveats 2 9 Output Report Syntax and Conventions 2 9 Security 2 10 Example MXCS Configuration 2 10 Related Commands 2 11 MXCI Mode Command 2 12 Session Variables 2 12 MXCI Comment 2 12 3 Object Service Commands INFO SERVICE 3 2 Considerations INFO SERVICE 3 2 Output Report States INFO SERVICE 3 3 Examples INFO SERVICE 3 3 START SERVICE 3 4 Considerations START SERVICE 3 4 Example START SERVI
111. urity on page 2 10 The user object assigns access permission for an administrator of the MXCS configuration database User or Operator The permission of User maps internally to TABLE READ The permission of Operator maps to TABLE READ and TABLE WRITE This object does not support grant permission Format of the user s name within the commands for the user object is the same as the NonStop OS group and name format groupname membername with these considerations e You can default both name components lf you default only groupname provide the leading dot You do not have to add quote marks e Names are not case sensitive in input However command execution sets the name to uppercase even if it is enclosed in quotes The two default user names and permissions are e PUBLIC with User permissions SUPER SUPER with Operator permissions You cannot remove or change these default user names The PUBLIC entry gives everyone User permissions Use the ADD USER command to assign Operator permissions to a few users SQL MX Connectivity Service Administrative Command Reference 526350 005 7 1 Object User Commands ADD USER ADD USER This command adds one user name and permissions to the MXCS configuration database access list Command syntax is ADD USER obj name PERM perm val obj name system name groupname membername system name is the name of a group of up to 16 CPUs with the sa
112. ver count is the upper limit on the servers that are operational for this service on this DS Valid values are 0 through the total number of ports allowed minus 3 See documentation on the MXOAS command for the total number of ports allowed The practical limit can be different for each service and is often in the range of 20 to 500 A value of 0 gives the system default which is a value determined by the system at run time SQL MX Connectivity Service Administrative Command Reference 526350 005 5 8 Object DS Commands ALTER DS IdleServer count is the lower limit on the available idle servers that are operational for this service on this DS Valid values are 0 through MaxServer count with 0 as the default This count represents idle servers that are waiting for user connections At DS startup once the InitServer count is satisfied additional servers are started until the IdleServer count is reached Initially idle servers are started in blocks of five with a check for incoming connection requests occurring between each block After peak user loads idle servers are terminated to the IdleServer count value see IdleTimeout on this page InitServer count is the suggested number of servers that each service starts when the DS first starts Legal values are from 0 to the smaller of either 1000 or the value specified by MaxServer count with the default value as 0 If the initial server count exceeds 1000 an error is
113. vironment variables to define session variables These are not expanded in the input command by MXCI or MXCS MXCI Comment An MXCI comment Begins with two hyphens and ends at the end of the line Can be ona line by itself or it can follow command text Can be embedded in multiline input provided it is outside of keywords and literals SQL MX Connectivity Service Administrative Command Reference 526350 005 2 12 3 Object Service Commands This section describes the MXCS administrative commands you use for the service object see Valid Command and Object Type Pairs on page 2 3 e INFO SERVICE on page 3 2 START SERVICE on page 3 4 STOP SERVICE on page 3 5 e VERSION SERVICE on page 3 7 The service object represents one running MXCS ODBC instance on a single CPU One system can have several service objects running simultaneously on the same or different CPUs However each service on the system requires a unique set of NonStop TCP IP ports assigned to it at start up The service object consists of one association server process plus one configuration server process and it can own several DS instances and server objects The stop and start service commands do not initiate or terminate the association server process Use the TACL commands RUN MXOAS and STOP to initiate and terminate the server process and to also name the service object For examples of these commands see Appendix A Example Commands and Ob
114. w quickly the command stops the service DSs and servers by using these key values NOW terminates all servers immediately A client connected to the server receives the error communication link failure onthe next action that accesses the server The client can disconnect and connect to another server or quit Incomplete transactions are rolled back we ISCONNECT closes the servers only after the remote client terminates the connection A client connected to a server does not know a termination is requested and can continue working until it disconnects normally This is the default mode SQL MX Connectivity Service Administrative Command Reference 526350 005 3 5 Object Service Commands Considerations STOP SERVICE REASON text is anonempty SQL string literal of up to 70 characters which indicates why the service is being shut down It is written to the EMS log by the service if the command is accepted Strings of more than 70 characters are truncated with a warning Single quotes are required Considerations STOP SERVICE e STOP SERVICE is a sensitive command The asterisk wild card is not supported Service goes to the stopped state only when all active DSs and servers have also transitioned to the stopped state New clients cannot connect to a server associated with a stopping or stopped service The administrator can check progress by using the INFO command The association server and the c
115. y uppercased during command execution which can cause errors Enter the default ds name as TMD Default _DataSource Considerations START DS e START DS is a sensitive command The asterisk wild card is not supported for DS name Example START DS This example starts the DS TDM_Defau CS gt start ds SAS TI DM_ 1t_DataSource for the service SAS Default_ DataSource START DS ODBC SAS TDM Default DataSource Successful SQL MX Connectivity Service Administrative Command Reference 526350 005 5 20 Object DS Commands STOP DS STOP DS This command stops one DS on all services or all DSs on one service The actual termination occurs at different times depending on the stop mode attribute you specify The DS goes to the stopped state only after all servers are stopped Note Use INFO DS to determine when a DS is in the STOPPED state Command syntax is STOP DS obj name REASON text AFTER stop mode obj name system name Sservice name ds name system name is the name of the current system of up to 16 CPUs with the same Expand address and where the target MXCS process is running syst em name and service name identify one service instance service name is the name of the MXCS association server that handles or processes the command where this DS should be stopped Using the asterisk wild card
116. ype Pairs on page 2 3 INFO SERVER on page 4 2 e STOP SERVER on page 4 5 SQL MX Connectivity Service Administrative Command Reference 526350 005 4 1 Object Server Commands INFO SERVER INFO SERVER This command displays attributes state connection and configuration of MXCS servers You cannot change these attributes directly Command syntax is INFO SERVER obj name DETAIL DS ds name obj name DS system name Sservice name Sserver name system name is the name of the current system of up to 16 CPUs with the same Expand address and where the target MXCS process is running syst em name and service name identify one service instance service name is the name of the MXCS association server process that owns this server server name is the name of the MXCS server process to be displayed It must not be an association or configuration server process It can be the asterisk wild card DETAIL displays all attributes If you omit this option the report provides only the most commonly used attributes When more details are needed especially for the client side this option provides additional status The server must be connected to retrieve useful information for a detailed display ds name is the name of the DS to be used to select a subset of all MXCS servers on this service This option is supported only when the server name specified

SQL/MX Connectivity Service Administrative Command Reference

Contents

Download Pdf Manuals

Related Search

Related Contents