> # B SequeLink® Manager Commands

> This appendix lists all available SequeLink Manager commands in alphabetical order. See "Invoking the SequeLink® Manager Command-Line Tool" for information about starting the SequeLink Manager Command-Line Tool.

> IMPORTANT:

> - SequeLink Manager command names are not case-sensitive; however, the command parameter service_name is case-sensitive.
> - If the value of a command parameter contains spaces, the value must be enclosed within single quotes (') or double quotes (").
> - If the value of a command parameter contains single or double quotes, use single quotes to quote double quotes and double quotes to quote single quotes.
> - The pound sign (#) is a comment character. All text that follows the pound sign on the same line is ignored.
> - When issuing commands using the direct or batch method, you must specify all of a command's required and optional parameters in the correct position (specify the parameters in the order they are documented). See "Direct Command Execution" and "Batch Command Execution" for more information about direct and batch methods of issuing commands.

> ### About | a

> Prints to the console the version of the SequeLink Manager Command-Line Tool and copyright information.

> Syntax

> `{about | a}`

> Example

>     about

> ### ActivateLocalConfig | alc

> Connects to the SequeLink Agent on a local machine.

> Syntax

> {`ActivateLocalConfig | alc`}

> Example

>     alc

> ### ActivateOfflineConfig | aoc

> Opens the local configuration file.

> Syntax

> {`ActivateOfflineConfig | aoc`} `configuration_file`

> where `configuration_file` is the path and name of local configuration file.

> Example

>     aoc "c:\Program Files\DataDirect\slserver60\cfg\swandm.ini"

> NOTE: The path is enclosed in quotes because there is a space in the path name. Otherwise, the path would not have to be quoted, for example, `aoc c:\DataDirect\cfg\swandm.ini`.

> ### ActivateRemoteConfig | arc

> Connects to a remote SequeLink Agent.

> Syntax

> {`ActivateRemoteConfig | arc`} `agent_connection_info`

> where `agent_connection_info` is the information required to connect to the SequeLink Agent-host:port, which is the host name and port of the server on which the SequeLink Agent resides.

> Example

>     arc caspar.ddtek.com:19996

> ### ActivateSecureRemoteConfig | asrc

> On Linux/UNIX/Windows, connects to a remote SequeLink Agent using SSL.

> Syntax

> {`ActivateSecureRemoteConfig | asrc`} `agent_connection_info`

> where `agent_connection_info` is the information required to connect to the SequeLink Agent-host:port, which is the host name and port of the server on which the SequeLink Agent resides.

> Example

>     asrc caspar.ddtek.com:19996

> ### CloseConfig | cc

> Closes the activated configuration.

> Syntax

> {`CloseConfig | cc`}

> Example

>     cc

> ### DataSourceAttributeAdd | dsaa

> Adds an attribute to the specified server data source and the specified SequeLink service.

> Syntax

> {`DataSourceAttributeAdd | dsaa`} `service_name data_source_name attribute_name value`

> where:

> `service_name` is the name of a data access service. Service names can be obtained using the ServiceList | sl command.

> `data_source_name` is the name of the server data source for which you want to add an attribute. This server data source must belong to the data access service you specified.

> `attribute_name` is the name of the attribute you want to add.

> value is the value for the attribute.

> See "SequeLink® Service Attributes" for a list of SequeLink service attributes and their valid values.

> Example

> In the following example, the DataSourceCurrentCatalog attribute is being added to the DS_Employees server data source that belongs to the SLOracle10 data access service. The value for the attribute is employees.

>     dsaa SLOracle10 DS_Employees DataSourceCurrentCatalog
>     employees

> ### DataSourceAttributeDelete | dsad

> Deletes an attribute from a server data source.

> Syntax

> {`DataSourceAttributeDelete | dsad`} `service_name data_source_name attribute_name`

> where:

> `service_name` is the name of a data access service. Service names can be obtained using the ServiceList | sl command.

> `data_source_name` is the name of the server data source from which you want to delete an attribute. This server data source must belong to the data access service you specified.

> `attribute_name` is the name of the attribute you want to delete.

> See "SequeLink® Service Attributes" for a list of SequeLink service attributes and their valid values.

> Example

> The following example deletes the DataSourceCurrentCatalog attribute from the DS_Employees server data source that belongs to the SLOracle10 data access service:

>     dsad SLOracle10 DS_Employees DataSourceCurrentCatalog

> ### DataSourceAttributeReplace | dsar

> Changes the value of a server data source attribute.

> Syntax

> {`DataSourceAttributeReplace | dsar`}`service_name data_source_name attribute_name value`

> where:

> `service_name` is the name of a data access service. Service names can be obtained using the ServiceList | sl command.

> `data_source_name` is the name of the server data source you want to modify. This server data source must belong to the data access service you specified.

> `attribute_name` is the attribute for which you want to change the value.

> `value` is the new value of the attribute.

> See "SequeLink® Service Attributes" for a list of SequeLink service attributes and their valid values.

> Example

> The following example changes the value of the DataSourceCurrentCatalog attribute in the DS_Employees server data source that belongs to the SLOracle10 data access service. The value is changed to partners.

>     dsar SLOracle10 DS_Employees DataSourceCurrentCatalog
>     partners

> ### DataSourceCreate | dsc

> Creates a server data source.

> Syntax

> {`DataSourceCreate | dsc`} `service_name data_source_name`

> where:

> `service_name` is the name of the data access service in which to create the new server data source.

> `data_source_name` is the name of the server data source you want to create.

> Example

> The following example creates a server data source named DS_Employess within the SLOracle10 data access service:

>     dsc SLOracle10 DS_Employees

> ### DataSourceDelete | dsd

> Deletes a server data source.

> Syntax

> {`DataSourceDelete | dsd`} `service_name data_source_name`

> where:

> `service_name` is the name of the data access service from which to delete a server data source. Service names can be obtained using the ServiceList | sl command.

> `data_source_name` is the name of the server data source you want to delete.

> Example

> The following example deletes the DS_Employees server data source from the SLOracle10 data access service:

>     dsd SLOracle10 DS_Employees

> ### DataSourceInfo | dsi

> Lists all attributes and their values for a server data source.

> Syntax

> {`DataSourceInfo | dsi`} `service_name data_source_name`

> where:

> `service_name` is the name of a data access service. Service names can be obtained using the ServiceList | sl command.

> `data_source_name` is the name of the server data source for which you want to list attributes and their values. This server data source must belong to the data access service you specified.

> See "SequeLink® Service Attributes" for a list of SequeLink service attributes and their valid values.

> Example

> The following example lists attributes and their values for the DS_Employees server data source. This server data source belongs to the SLOracle10 data access service.

>     dsi SLOracle10 DS_Employees

> ### DataSourceList | dsl

> Lists all available SequeLink server data sources.

> Syntax

> {`DataSourceList | dsl`}

> Example

>     dsl

> ### Echo | e

> Echoes a user-defined string. This command is useful when you issue commands from a file. For example, you could issue the DataSourceCreate command and use the Echo command to display text that says "A new data source was created in the SLOracle10 data access service."

> Syntax

> {`Echo | e`} `string`

> where `string` is the text you want displayed to your console. If the string contains spaces, you must surround the string with either double or single quotes.

> Example

>     echo "Testing echo command."

> ### EventList | el

> Lists events from a specified data access service or from a specified event trace file.

> Syntax

> {`eventlist | el`} `service_name` | [remote]file=`event_trace_file_name
> `[details]
> [ [{service | srvc}] |
> [{session | sess}] |
> [{statement | stmt}] |
> [{transaction | trans}] |
> [{network | net}] |
> [{error | err}] |
> [{other | oth}] ] ]
> [count=[{ + | - }] {all | `number`}]
> [offset={begin | end} [{ + | - }]`number`]
> [query='custom_event_filter_string']

> where:

> `service_name` is the name of a data access service. The event trace file for this specified service will be listed. Service names can be obtained using the ServiceList | sl command.

> `event_trace_file_name` is the path and name of the event trace file you want to list.

> `number` is the event number of events to list when used with the count option. When used with the offset option, number is the number of the event from which to start listing events. For example, if offset=10, SequeLink would list all events starting with event 10. Another example, if you specify count=20 and offset=begin, SequeLink will list the first 20 events. If you specify count=20 and offset=5, SequeLink will list 20 events starting from event 5.

> `custom_event_filter_string` is an event filter statement. See "Filtering Events" for more information.

> Options

> Details: If you specify Details, SequeLink will list detail information about the event.

> Event Types: You can specify one or more of the following event groups for which to list event information: Service, Session, Statement, Transaction, Error, or Other. When you specify one or more of the event groups, SequeLink Manager lists all the events of the type you specified. For example, if you specify Service, SequeLink lists all service events such as Service Started and Service Stopping (these events start with "Service"). Event names that do not start with Service, Session, Network, Error, Statement, or Transaction are Other events (for example, Cursor Closed).

> Examples

> Local host or remote configuration examples:

> Example A: The following example lists detailed event information for the SLAgent service:

>     el SLAgent details

> Example B: The following example lists detailed event information for all service events starting with event number 10 in the event trace file associated with the SLOracle data access service:

>     el SLOracle details service count=all offset=10

> Example C: The following example defines a query for the information it will list for the SLOracle10 data access service. The query returns all SQL statements that do not return a return code of 0.

>     el SLOracle10 stmt query='${ReturnCode} != 0'

> Example D: The following example lists event information for the first 10 events in the local file named SLoracle10.trc:

>     el "file=C:\Program Files\DataDirect\slserver60\tracing\
>     SLoracle10.trc" count=10

> Example E: The following example lists detailed event information for only service events in the remote file named SLoracle10.trc:

>     el "remotefile=C:\Program Files\DataDirect\slserver60\
>     tracing\SLOracle10.trc" service details

> Offline configuration examples:

> Example A: The following example lists event information from the local file named SLoracle10.trc file:

>     el "file=C:\Program Files\DataDirect\slserver60\tracing\
>     SLOracle10.trc"

> Example B: The following example lists event information for the first 10 events in the local file named SLoracle10.trc:

>     el "file=C:\Program Files\DataDirect\slserver60\tracing\
>     SLOracle10.trc" count=10

> Example C: The following example lists event information from the local file named SLoracle10.trc, starting from the end of the file and listing all events:

>     el "file=C:\Program Files\DataDirect\slserver60\tracing\
>     SLOracle10.trc" count=-all offset=end

> Example D: The following example lists only session and service event information from the local file named SLoracle10.trc, starting with the fifth event:

>     el "file=C:\Program Files\DataDirect\slserver60\tracing\
>     SLOracle10.trc" offset=5 service session

> Example E: The following example lists detailed event information for service events only from the local file named SLoracle10.trc:

>     el "file=C:\Program Files\DataDirect\slserver60\tracing\
>     SLOracle10.trc" service details

> ### EventExport | ee

> Exports events from a specified service or specified event trace file to a text file or XML file.

> Syntax

> {`eventexport | ee`} `service_name` | [remote]file=`event_trace_file_name` `export_format` `export_file_name` | [remote]file=event_trace_file_name|
> [ [ [{service | srvc}] |
> [{session | sess}] |
> [{statement | stmt}] |
> [{transaction | trans}] |
> [{network | net}] |
> [{error | err}] |
> [{other | oth}] ] ]
> [count=[{ + | - }] {all | `number`}]
> [offset={begin | end} [{ + | - }]`number`]
> [query='`custom_event_filter_string`']

> where:

> `service_name` is the name of a data access service. The event trace file from the specified service is listed. Service names can be obtained using the ServiceList | sl command.

> `event_trace_file_name` is the path and name of the event trace file.

> `export_format` is the format of the file to which you want to export the events, where:

> - {delimited_txt | deltxt} is a text file with commas separating each event you export
> - {raw_xml | rxml} is a well-formed XML file.
> - {validated_xml | vxml} is a valid XML file.

> `export_file_name` is the path and name of the file to which you are exporting the events.

> `number` is the event number of events to export when used with the count option. When used with the offset option, number is the number of the event from which to start exporting events. For example, if offset=10, SequeLink would export all events starting with event 10. Another example, if you specify count=20 and offset=begin, SequeLink will export the first 20 events. If you specify count=20 and offset=5, SequeLink will export 20 events starting from event 5.

> `custom_event_filter_string` is an event filter statement. See "Filtering Events".

> Options

> Event Types: You can specify one or more of the following event groups for which to export event information: Service, Session, Statement, Transaction, Error, or Other. When you specify one or more of the event groups, SequeLink Manager exports all the events of the type you specified. For example, if you specify Service, SequeLink exports all service events such as Service Started and Service Stopping (these events start with "Service"). Event names that do not start with Service, Session, Network, Error, Statement, or Transaction are Other events (for example, Cursor Closed).

> Examples

> Local host or remote configuration examples:

> Example A: The following example exports event information in the local file named SLoracle10.trc to a text file named export.txt:

>     ee "file=C:\Program Files\DataDirect\slserver60\tracing\
>     SLOracle10.trc" deltxt export.txt

> Example B: The following example exports event information for only service events in the remote file named SLoracle10.trc to a valid XML file named export.xml:

>     ee "remotefile=C:\Program Files\DataDirect\slserver60\
>     tracing\SLOracle10.trc" vxml export.xml service

> Example C: The following example exports event information for all service events starting with event number 10 in the event trace file associated with the SLOracle data access service to a well-formed XML file named export.xml:

>     ee SLOracle rxml export.xml service count=all offset=10

> Example D: The following example exports session event information for the SLAgent service to a text file named export.txt:

>     ee SLAgent deltxt export.txt

> Example E: The following example defines a query for the information it will export for the SLOracle10 data access service to a valid XML file named export.xml. The query returns all SQL statements that do not return a return code of 0:

>     ee SLOracle10 vxml export.xml stmt
>     query='${ReturnCode} != 0'

> Offline configuration examples:

> Example A: The following example exports event information from the local file named SLOracle10.trc to a text file named export.txt:

>     ee "file=C:\Program Files\DataDirect\slserver60\tracing\
>     SLOracle10.trc" deltxt export.txt

> Example B: The following example exports event information for the first 10 events in the local file named SLoracle10.trc to a text file named export.txt:

>     ee "file=C:\Program Files\DataDirect\slserver60\tracing\
>     SLOracle10.trc" deltxt export.txt count=10

> Example C: The following example exports event information from the local file named SLoracle10.trc, starting from the end of the file and listing all events, to a well-formed XML file named export.xml:

>     ee "file=C:\Program Files\DataDirect\slserver60\tracing\
>     SLOracle10.trc" rxml export.xml count=-all offset=end

> Example D: The following example exports only session and service event information from the local file named SLoracle10.trc, starting with the fifth event, to a well-formed XML file named export.xml:

>     ee "file=C:\Program Files\DataDirect\slserver60\tracing\
>     SLOracle10.trc" rxml export.xml offset=5 service session

> Example E: The following example exports event information for service events only from the local file named SLoracle10.trc to a valid XML file named export.xml:

>     ee "file=C:\Program Files\DataDirect\slserver60\tracing\
>     SLOracle10.trc" vxml export.xml service

> ### Exit | e

> Quits the SequeLink Manager Command-Line Tool.

> Syntax

> {Exit | e}

> Example

>     exit

> ### Help | ?

> Displays help about the syntax for invoking the command-line tool or displays help about individual commands.

> Syntax

> {`Help | ?`} [{`short_command_name` | `long_command_name`}]

> where:

> `short_command_name` is the short version of the command name. For example, e is the short version of the Echo command.

> `long_command_name` is the long version of the command name, for example, Echo.

> Example

> The following example displays help for the Echo command:

>     ? Echo

> ### MVSDB2InterfaceAttributeAdd | mdiaa

> Adds an attribute to a DB2 interface.

> Syntax

> {MVSDB2InterfaceAttributeAdd | mdiaa} DB2_interface_ID attribute_name value

> where:

> DB2_interface_ID identifies the DB2 interface.

> attribute_name is the attribute you want to add.

> value is the value of the attribute.

> Example

> The following example adds the MVSDB2RootDescription attribute to DB2_Interface. The value is set to DB2v9.1.

>     mdiaa DB2_interface MVSDB2RootDescription DB2v9.1

> ### MVSDB2InterfaceAttributeDelete | mdiad

> Deletes an attribute for a DB2 interface.

> Syntax

> {MVSDB2InterfaceAttributeDelete | mdiad} DB2_interface_ID attribute_name

> where:

> DB2_interface_ID identifies the DB2 interface from which you want to delete an attribute.

> attribute_name is the name of the attribute you want to delete.

> Example

> `mdiad DB2_Interface MVSDB2RootDescription`

> ### MVSDB2InterfaceAttributeReplace | mdiar

> Changes the value of a DB2 interface attribute.

> Syntax

> {MVSDB2InterfaceAttributeReplace | mdiar} DB2_interface_ID attribute_name value

> where:

> DB2_interface_ID identifies the DB2 interface.

> attribute_name is the name of the attribute you want to change.

> value is the new value of the attribute.

> Example

> The following example changes the value of the MVSDB2TraceTableSize attribute to 256:

>     mdiar DB2_Interface MVSDB2TraceTableSize 256

> ### MVSDB2InterfaceInfo | mdii

> Lists all attributes and their values for a DB2 interface.

> Syntax

> {MVSDB2InterfaceInfo | mdii} DB2_interface_ID

> where DB2_interface_ID identifies the DB2 interface for which you want to list attributes and their values.

> Example

>     mdii DB2_Interface

> ### MVSDB2InterfaceList | mdil

> Lists all available external DB2 interfaces.

> Syntax

> {MVSDB2InterfaceList | mdil}

> Example

>     mdil

> ### MVSGlobalAttributeDelete | mgad

> Deletes an attribute in the z/OS global settings.

> Syntax

> {MVSGlobalAttributeDelete | mgad} attribute_name

> where attribute_name is the name of the attribute you want to delete.

> Example

>     mgad MVSGlobalCompTrace

> ### MVSGlobalAttributeReplace | mgar

> Changes the value of the specified attribute in the z/OS global settings.

> Syntax

> {MVSGlobalAttributeReplace | mgar} attribute_name value

> where:

> attribute_name is the name of the attribute you want to change.

> value is the new value of the attribute.

> Example

>     mgar MVSGlobalCompTrace D

> ### MVSGlobalInfo | mgi

> Lists all attributes and their values for the z/OS global settings.

> Syntax

> {MVSGlobalInfo | mgi}

> Example

>     mgi

> ### MVSUserIDMapAttributeAdd | muimaa

> Adds an attribute to a user ID map.

> Syntax

> {MVSUserIDMapAttributeAdd | muimaa} user_ID_map attribute_name value

> where:

> user_ID_map is the user ID map to which you want to add an attribute.

> attribute_name is the name of the attribute you want to add.

> value is the value of the attribute.

> Example

> The following example adds the MVSUIDDefaultAccess attribute to the UserID1 user ID map. The value is set to PERMIT.

>     miumaa UserID1 MVSUIDDefaultAccess PERMIT

> ### MVSUserIDMapAttributeDelete | muimad

> Deletes an attribute for a user ID map.

> Syntax

> {MVSUserIDMapAttributeDelete | muimad} user_ID_map attribute_name

> where:

> user_ID_map is the user ID map from which you want to delete an attribute.

> attribute_name is the name of the attribute you want to delete.

> Example

>     miumad UserID1 MVSUIDDefaultAccess

> ### MVSUserIDMapAttributeReplace | muimar

> Changes the value for a user ID map attribute.

> Syntax

> {MVSUserIDMapAttributeReplace | muimar} user_ID_map attribute_name value

> where:

> user_ID_map identifies the user ID map.

> attribute_name is the name of the attribute you want to change.

> value is the value of the attribute.

> Example

>     miumar UserID1 MVSUIDDefaultAccess DENY

> ### MVSUserIDMapInfo | muimi

> Lists all attributes and their values for a user ID map.

> Syntax

> {MVSUserIDMapInfo | muimi} user_ID_map

> where user_ID_map is the user ID map for which you want to list attributes and their values.

> Example

>     muimi UserID1

> ### MVSUserIDMapList | muiml

> Lists all available user ID maps.

> Syntax

> {MVSUserIDMapList | muiml}

> Example

>     miuml

> ### NoOperation | noop

> Performs no operation.

> Syntax

> {`NoOperation | noop`}

> Example

>     noop

> ### ProfileEventTraceCreate | petc

> Creates an event trace profile for a SequeLink service.

> Syntax

> {`ProfileEventTraceCreate | petc`} `service_name`

> where `service_name` is the service for which you want to create the event trace profile.

> Example

>     petc SLOracle10

> ### ProfileEventTraceDelete | petd

> Deletes an event trace profile for a SequeLink service.

> Syntax

> {`ProfileEventTraceDelete | petd`} `service_name`

> where `service_name` is the service from which you want to delete an event trace profile. Service names can be obtained using the ServiceList | sl command.

> Example

>     petd SLOracle10

> ### ProfileEventTraceEdit | pete

> Changes an event trace profile for a SequeLink service.

> Syntax

> {`ProfileEventTraceEdit | pete`} `service_name` {enable | disable | `event_group`} [{enable | disable} | {`event_name` | `event_id`} [{on | off}]] [`custom_event_filter`]

> where:

> `service_name` is the service for which to change an event trace profile. This is a requirement value. Service names can be obtained using the ServiceList | sl command.

> `event_group` is the type of event within the service to change. Valid values are:

> - {Service | srvc}
> - {Session | sess}
> - {Statement | stmt}
> - {Transaction | trans}
> - {Network | net}
> - {Error | err}
> - {Other | oth}

> `event_name` is the name of the event within in the specified event group to change. You can use the ProfileEventTraceInfo command to list available event names.

> `event_id` is the numeric identifier of the event within the specified event group to change. You can specify either `event_name` or `event_id`, not both. You can use the ProfileEventTraceInfo command to list available event identifiers.

> `custom_event_filter` is an optional event filter that can be specified for all events being enabled. See "Filtering Events" for more information.

> Examples

> Example A: The following example disables all events for the SLOracle10 data access service, meaning that no events are written to the event trace file:

>     pete SLOracle10 disable

> Example B: The following example enables the event specified by the custom event filter:

>     pete SLOracle10 Session enable '${ClientInfo}="127.0.0.1"'

> Example C: The following example enables all service events for the `SLOracle10` data access service:

>     pete SLOracle10 service enable

> Example D: The following example disables all error events for the SLOracle10 data access service:

>     pete SLOracle10 err disable

> Example E: The following example changes the state of the transaction event named Transaction Rollback to off:

>     pete SLOracle10 trans "Transaction Rollback" off

> Example F: The following example changes the state of the session event identified by 2 to "on" if the event meets the custom event query filter:

>     pete SLOracle10 sess 2 on '${DbmsUser} = "scott"'

> ### ProfileEventTraceInfo | peti

> Lists event trace profile information for a SequeLink service.

> Syntax

> `{ProfileEventTraceInfo | peti`} `service_name`

> where `service_name` is the service for which to list event trace profile information. Service names can be obtained using the ServiceList | sl command.

> Example

>     peti SLOracle10

> ### ProfileMonitorCreate | pmc

> Creates a monitoring profile for a SequeLink service.

> Syntax

> {`ProfileMonitorCreate | pmc`} `service_name` {yes | no}

> where `service_name` is the service for which you want to create the monitoring profile.

> You must specify either yes or no. Yes indicates that shared counters will be enabled. No indicates that shared counters will not be enabled. Enabling shared counters is for Windows only.

> Example

>     pmc SLOracle10

> ### ProfileMonitorDelete | pmd

> Deletes a monitoring profile for a SequeLink service.

> Syntax

> {`ProfileMonitorDelete | pmd`} `service_name`

> where `service_name` is the service from which you want to delete the monitoring profile. Service names can be obtained using the ServiceList | sl command.

> Example

>     pmd SLOracle10

> ### ProfileMonitorEdit | pme

> Changes a monitoring profile for a SequeLink service.

> Syntax

> {`ProfileMonitorEdit | pme`} `service_name` {enable | disable | `event_group`} [{enable | disable} | {event_name | event_id} [{on | off}]]

> where:

> `service_name` is the service for which to change the monitoring profile. Service names can be obtained using the ServiceList | sl command.

> `event_group` is the type of event to change for the monitoring profile. Valid values are:

> - {Service | srvc}
> - {Session | sess}
> - {Statement | stmt}

> event_name is the name of the event within in the specified event group to change. You can use the ProfileMonitorInfo command to list available event names.

> event_id is the numeric identifier of the event within the specified event group to change. You can specify either event_name or event_id, not both. You can use the ProfileMonitorInfo command to list available event identifiers.

> Examples

> Example A: The following example enables all events for the SLOracle10 data access service, meaning that all events are monitored:

>     pme SLOracle10 enable

> Example B: The following example disables all events for the SLOracle10 data access service, meaning no events are monitored:

>     pme SLOracle10 disable

> Example C: The following example enables all service events for the SLOracle10 data access service:

>     pme SLOracle10 service enable

> Example D: The following example disables all session events for the SLOracle10 data access service:

>     pme SLOracle10 session disable

> Example E: The following example changes the state of the session event named database user to off:

>     pme SLOracle10 session "database user" off

> Example F: The following example changes the state of the session event identified by 10 to off:

>     pme SLOracle10 session 10 off

> Example G: The following example changes the state of the statement event named sql to on:

>     pme SLOracle10 stmt sql on

> ### ProfileMonitorInfo | pmi

> Lists profile monitoring information for a SequeLink service.

> Syntax

> {`ProfileMonitorInfo | pmi`} `service_name`

> where `service_name` is the service for which you want to list profile monitoring information. Service names can be obtained using the ServiceList | sl command.

> Example

>     pmi SLOracle10

> ### Quit | q

> Quits the SequeLink Manager Command-Line Tool.

> Syntax

> {`Quit | q`}

> Example

>     q

> ### SaveConfig | save

> Saves the current configuration. This command is available only when AutoSave setting is set to off. For more information about setting AutoSave, see the Set | s command.

> Syntax

> {`SaveConfig | save`}

> Example

>     save

> ### ServiceActiveDebugLogLevel | sadll

> Displays or changes the debug log level of an active SequeLink service. When no debug log level values are provided, the current settings are listed.

> Syntax

>     {ServiceActiveDebugLogLevel | sadll} service_name
>     [ [{dis | disable}]
>     [{enall |  enableall}]
>     [{en | enable}]
>     [{ferr | fatalerror}={off | on}] |
>     [{err | errors=off | on}] |
>     [{war | warnings}={off | on}] |
>     [{info | informationals}={off | on}] |
>     [{debug | debugging}={off | on}] |
>     [{sspp | ssppackets}={off | on}] |
>     [{sspr | ssprequests}={off | on}] | ... ]

> where service_name is the active service for which you want to display or change debug log levels. Service names can be obtained using the `ServiceList | sl` command.

> Example

> The following example turns on debug messages and turns off error messages in the debug log for the SLOracle10 data access service:

>     sadll SLOracle10 debug=on err=off

> ### ServiceActiveInfo | sai

> Lists specific information about an active SequeLink service.

> Syntax

> {`ServiceActiveInfo | sai`} `service_name`

> where `service_name` is the active service for which you want to list information. Service names can be obtained using the ServiceList | sl command.

> Example

>     sai SLOracle10

> ### ServiceAttributeAdd | saa

> Adds an attribute to a SequeLink service.

> Syntax

> {`ServiceAttributeAdd | saa`} `service_name` `attribute_name` `value`

> where:

> `service_name` is the service to which you want to add an attribute. Service names can be obtained using the ServiceList | sl command.

> `attribute_name` is the name of the attribute you want to add.

> `value` is the value of the attribute.

> See "SequeLink® Service Attributes" for a list of SequeLink service attributes and their valid values.

> Example

>     saa SLOracle10 ServiceUser sqlnk

> ### ServiceAttributeDelete | sad

> Deletes an attribute from a SequeLink service.

> Syntax

> {`ServiceAttributeDelete | sad`} `service_name` `attribute_name`

> where:

> `service_name` is the service from which you want to delete an attribute. Service names can be obtained using the ServiceList | sl command.

> `attribute_name` is the name of the attribute you want to delete.

> See "SequeLink® Service Attributes" for a list of SequeLink service attributes and their valid values.

> Examples

>     sad SLOracle10 ServiceCodePage
>     sad SLOracle10 ServiceUser[2]

> ### ServiceAttributeReplace | sar

> Changes the value for a SequeLink service attribute.

> Syntax

> {ServiceAttributeReplace | sar} `service_name` `attribute_name` value

> where:

> `service_name` is the service for which you want to change the value of an attribute. Service names can be obtained using the ServiceList | sl command.

> `attribute_name` is the name of the attribute you want to change.

> `value` is the new value of the attribute.

> See "SequeLink® Service Attributes" for a list of SequeLink service attributes and their valid values.

> Example

>     sar SLOracle10 ServiceUser[2] devuser

> ### ServiceCreate | sc

> NOTE: This command is not applicable to z/OS.

> Creates a SequeLink service based on a service template ID.

> Syntax

> {`ServiceCreate | sc`} `service_name` `service_ID` `tcp_port`

> where:

> `service_name` is the name of the service to create.

> `service_ID` identifies the ID of the service template to use to create the new service. To get a listing of available templates and their IDs, use the ServiceTemplateList | stl command.

> `tcp_port` is the TCP/IP port on which the service is listening.

> Example

>     sc SLOracle10 SL6_Oracle10 19996

> ### ServiceDebugLogLevel | sdll

> Displays or changes the debug log level of a SequeLink service. When no debug log level values are provided, the current settings are listed.

> Syntax

>     {ServiceDebugLogLevel | sdll} service_name
>     [ [{dis | disable}]
>     [{enall |  enableall}]
>     [{en | enable}]
>     [{ferr | fatalerror}={off | on}] |
>     [{err | errors=off | on}] |
>     [{war | warnings}={off | on}] |
>     [{info | informationals}={off | on}] |
>     [{debug | debugging}={off | on}] |
>     [{sspp | ssppackets}={off | on}] |
>     [{sspr | ssprequests}={off | on}] | ... ]

> where service_name is the service to which the session belongs. Service names can be obtained using the `ServiceList | sl` command.

> Example

> The following example turns on debug messages and turns off error messages in the debug log file for the SLOracle10 data access service:

>     sdll SLOracle10 debug=on err=off

> ### ServiceDelete | sd

> NOTE: This command is not applicable to z/OS.

> Deletes a SequeLink service.

> Syntax

> {`ServiceDelete | sd`} `service_name`

> where `service_name` is the name of the service you want to delete. Service names can be obtained using the ServiceList | sl command.

> Example

>     sd SLOracle10

> ### ServiceInfo | si

> Lists all attributes and their values for a SequeLink service.

> Syntax

> {`ServiceInfo | si`} `service_name`

> where `service_name` is the service for which you want to list attributes and their values. Service names can be obtained using the ServiceList | sl command.

> See "SequeLink® Service Attributes" for a list of SequeLink service attributes and their valid values.

> Example

>     si SLOracle10

> ### ServiceList | sl

> Lists all available SequeLink services.

> Syntax

> {`ServiceList | sl`}

> Example

>     sl

> ### ServiceRegister | sr

> NOTE: This command is not applicable to z/OS.

> Registers a SequeLink service.

> Syntax

> {`ServiceRegister | sr`} `service_name`

> where `service_name` is the service you want to register. Service names can be obtained using the ServiceList | sl command.

> Example

>     sr SLOracle10

> ### ServiceStart | ss

> NOTE: This command is not applicable to z/OS.

> Starts a SequeLink service.

> Syntax

> {`ServiceStart | ss`} `service_name`

> where `service_name` is the service you want to start. Service names can be obtained using the ServiceList | sl command.

> Example

>     ss SLOracle10

> ### ServiceStop | sst

> NOTE: This command is not applicable to z/OS.

> Stops a SequeLink service.

> Syntax

> {`ServiceStop | sst`} `service_name`

> where `service_name` is the service you want to stop. Service names can be obtained using the ServiceList | sl command.

> Example

>     sst SLOracle10

> ### ServiceTemplateList | stl

> Lists all available SequeLink service templates and their IDs.

> Syntax

> {`ServiceTemplateList | stl`}

> Example

>     stl

> ### ServiceTemplateInfo | sti

> Lists all attributes and their values for a SequeLink service template.

> Syntax

> {`ServiceTemplateInfo | sti`} `service_template_ID`

> where `service_template_ID` identifies the service template. To get a listing of available templates and their IDs, use the ServiceTemplateList | stl command.

> Example

>     sti SL6_Oracle10

> ### ServiceUnregister | su

> NOTE: This command is not applicable to z/OS.

> Unregisters the specified SequeLink service.

> Syntax

> {`ServiceUnregister | su`} `service_name`

> where `service_name` is the service you want to unregister. Service names can be obtained using the ServiceList | sl command.

> Example

>     su SLOracle10

> ### SessionDebugLogLevel | sesdll

> NOTE: This command is not applicable on Linux/UNIX or z/OS.

> Displays or changes the debug log level of the specified session. When no debug log level values are provided, the current settings are listed.

> Syntax

>     {SessionDebugLogLevel | sesdll} service_name
>     [ [{dis | disable}]
>     [{enall | enableall}]
>     [{en | enable}]
>     [{ferr | fatalerror}={off | on}] |
>     [{err | errors}={off | on}] |
>     [{war | warnings}={off | on}] |
>     [{info | informationals}={off | on}] |
>     [{debug | debugging}={off | on}] |
>     [{sspp | ssppackets}={off | on}] |
>     [{sspr | ssprequests}={off | on}] | ... ]

> where service_name is the service to which the session belongs. Service names can be obtained using the `ServiceList | sl` command.

> Examples

> Example A: The following example displays the current settings of the debug log for session 5 of the SLOracle10 data access service:

>     sesdll SLOracle10 5

> Example B: The following example turns on debug messages and turns off error messages in the debug log for session 5 of the SLOracle10 data access service:

>     sesdll SLOracle10 5 debug=on err=off

> ### SessionInfo | sesi

> Lists specific information about a session and its associated statements (only for data access sessions) for SequeLink service.

> Syntax

> {`SessionInfo | sesi`} `service_name` `session_ID`

> where:

> `service_name` is the service to which the session belongs. Service names can be obtained using the ServiceList | sl command.

> `session_ID` identifies the session for which you want to display information. This session must belong to the specified service. Session IDs can be obtained using the ServiceActiveInfo | sai command.

> Example

>     sesi SLOracle10 5

> ### SessionStop | sess

> Stops a session for a SequeLink service.

> Syntax

> {`SessionStop | sess`} `service_name` `session_ID`

> where:

> `service_name` is the service to which the session belongs. Service names can be obtained using the ServiceList | sl command.

> `session_ID` identifies the session you want to stop. This session must belong to the specified service. Session IDs can be obtained using the ServiceActiveInfo | sai command.

> Example

>     sess SLOracle10 5

> ### Set | s

> Sets the following configuration for the command-line tool settings. Valid values are:

> - AutoSave
> - Echo
> - IgnoreErrors

> AutoSave specifies whether to save the configuration when a change is made. When set to on, the configuration is saved when a change is made. When set to off, the configuration is not automatically saved, and you must issue a SaveConfig command to save the configuration.

> Echo specifies whether all commands entered on the command line are printed to output. When set to on, all commands entered on the command line are printed to output. When set to off, this setting is ignored. The default is off.

> IgnoreErrors specifies whether the SequeLink Manager Command-Line Tool stops when an error occurs. When set to on, the SequeLink Manager Command-Line Tool stops when an error occurs. This setting is useful when you want the processing of batch files to stop when an error occurs. When set to off, this setting is ignored. The default is off.

> Syntax

> {`Set | s`} [option1={on | off} [option2={on | off} ...] ]

> Examples

>     set autosave=off
>     set echo=on
>     set echo=on ignoreerrors=on