Keys and fields
In IBM® Sterling Control Center Monitor, you can specify a key to define the criteria for a report, rule, or SLC. You can also specify a key to act as a filter to limit the number of items that display in many IBM Sterling Control Center Monitor listings. A parameter consists of a key, an operator, and a value.
Statistics, properties, and other system-generated information are displayed in various listings, Activity Monitors, and Process Monitors. They give you information about alerts, file transfers, business processes, and other status information. These informational fields are also included here.
The keys and fields are listed in alphabetic order. For each key or field, a brief description is provided along with server-specific information, if applicable. For some items, mapping of terms is included to translate values to a specific server type. Not all keys are available for use in all situations.
|Action||Action performed on IBM Sterling Control Center Monitor entity.|
|Actions Flag||Time stamp indicated when event processing completed.|
|Activity Type||The type of activity an SLC event is associated with. Possible values include:
|Alert level||The severity level of the Alert. Possible values include:
|Batch ID||Batch identifier used in Sterling Connect:Enterprise®.|
|Batch Number||Batch number used in Sterling Connect:Enterprise.|
|Bytes Read||Number of bytes read from the source file by the sending server.|
|Bytes Received||Number of bytes received by the receiving server.|
|Bytes Sent||Number of bytes sent by the sending server to the receiving server.|
|Bytes Written||Number of bytes written to the destination file by the receiving server.|
|Check Point (Y or N)||Indicates whether the checkpoint feature of Sterling Connect:Direct® is enabled to facilitate recovery if an interruption in data transfer occurs.|
|Condition Code||Return code associated with Process steps and Process ends. Possible values include:
|Control Center Name||Name of the IBM Sterling Control Center Monitor event processor.|
|Cipher Suite||The cipher suite, such as SSL_RSA_WITH_DES_CBC_SHA, used in secure Sterling Connect:Direct sessions.|
|CX.Event Type||Event type. Possible values are:
|CX.File Bytes Transferred||File bytes transferred.|
|CX.File Label||File label (PeSIT pi37).|
|CX.File Transfer Protocol||File transfer protocol. Possible values are:
|CX.Local File Name||Local file name.|
|CX.Local Node Name||Local node name.|
|CX.Network Bytes Transferred||Network bytes transferred.|
|CX.Network Return Code||Network return code.|
|CX.Number of Records Transferred||Number of records transferred.|
|CX.Operating System||Operating system.|
|CX.Other Node Name||Other node name.|
|CX.Process Originator||Process originator. Possible values are:
|CX.Protocol Return Code||Protocol return code.|
|CX.Receiver of File||Receiver of the file.|
|CX.Request Type||Request type. Possible values are:
|CX.Return Code||System return code.|
|CX.Sender of File||Sender of the file.|
|CX.Server Name||Server name.|
|CX.System Return Code||Return code.|
|CX.Transfer Destination||Transfer destination.|
|CX.Transfer Direction||Transfer direction. Possible values are:
|CX.Transfer Identified||Transfer identified.|
|CX.Transfer Origin||Transfer origin.|
|CX.Type of Link||Type of link. Possible values are:
|CX.User Data Received||User data received (PeSIT Pi99), associated to file.|
|CX.User Data Sent||User data sent (PeSIT pi99), associated to file.|
|Daemon Host||DNS host name or IP address of the system the Sterling Connect:Enterprise daemon is on.|
|Daemon Name||Name of the Sterling Connect:Enterprise daemon.|
|Daemon Originator||Originator of the Sterling Connect:Enterprise daemon. Same as Remote ID.|
|Daemon PID||Process identifier of the Sterling Connect:Enterprise daemon.|
|Daemon Resource||Resource of the Sterling Connect:Enterprise daemon.|
|Daemon SID||Session identifier of the Sterling Connect:Enterprise daemon.|
|Daemon State||State of the Sterling Connect:Enterprise daemon.|
|Daemon Type||Type of the Sterling Connect:Enterprise daemon. IBM Sterling Control Center Monitor monitors only daemons of type master.|
|Data Visibility Group||Name of the data visibility group.
Note: If the user who creates a rule or SLC is data visibility restricted, a data visibility group must be specified.
|Date Time||The date and time that the event was generated.
For FTP W3C servers and IIS logs, this value can be the date and time when the event started or ended. For date and time for end events, this value is the date time plus the time taken.
|Days Before Expiry||Number of days before a certificate expires.|
|Dest Agent||Destination MQ MFT Agent.|
|Dest Disp1||The status of the destination file before the transfer begins.|
|Destination File||Destination file name.
For Sterling Connect:Direct, the file name at the destination in a copy step of a Process.
For Sterling Connect:Enterprise the file name, if received by Sterling Connect:Enterprise, or the userid requesting the file if sent by Sterling Connect:Enterprise.
For FTP, in a PUT, the name of the file as found in the FTP transfer log. In a GET, the ID of the user who initiated the transfer.
For FTP W3C servers, in the case of an inBound destination file, check the cs-uri-stem if the FTP command is in the cs-method field. Otherwise, check the cs-uri-query field.
For FTP W3C servers, in the case of an outBound destination file, check the cs-username if available. Otherwise, check the c-ip field.
For FTP IIS logs, in the case of an inBound destination file, check the cs-uri-stem. For an outBound destination file, check the cs-username field.
For Global Mailbox, indicates the file name at the destination in a file transfer.
|Direction (inBound or outBound)||Indicates direction of Sterling B2B Integrator, FTP, and Global Mailbox file transmissions.
For FTP W3C servers, depends on the FTP command. SENT, RETR, GET, and DOWNLOADED commands are considered inbound. CREATED, STOR, STOU, PUT, UPLOADED, APPE, and APPENDED commands are considered outbound.
For FTP IIS logs, depends on the FTP command in the cs-method field.
|EMail Flag||Indicates when email action processing completed.|
|Event ID||The ID number assigned by the system to each event.|
|Event ID/Number||The ID number assigned by the system to each event.|
|Event Type||A code that indicates the type of event.|
|Executing Processes||The number of Processes in the Execution queue.|
|Extended Compression||Indicates whether the extended compression was used while transferring the file.|
|FASP Bandwidth||Indicates how much bandwidth each FASP-enabled IBM Sterling Connect:Direct transfer can use.|
|FASP Enabled||Indicates whether FASP is enabled for IBM Sterling Connect:Direct transfers.
Yes = FASP is enabled for IBM Sterling Connect:Direct transfers.
No = FASP is not enabled for IBM Sterling Connect:Direct transfers.
|FASP File Size Threshold||The threshold that restricts small files from being sent by an IBM Sterling Connect:Direct server that uses FASP. If the file size is less than the threshold, the file is sent by a TCP or IP address. The threshold is a numeric value in KB, MB, or GB that is greater than or equal to 10 MB. The default is 1G.|
|FASP Policy||The FASP policy being used for an IBM Sterling Connect:Direct transfer. Possible values include:
|FASP Supported||Indicates whether FASP is supported for a Sterling Connect:Direct server.
True = FASP is supported for a IBM Sterling Connect:Direct server.
False = FASP is not supported for a IBM Sterling Connect:Direct server.
|Feedback||The feedback code generated from a Sterling Connect:Direct Process statement.|
|fgActivityType||The activity associated with the Sterling File Gateway file transfer. Possible values include:
|FG.Activity (A or R or D)||The activity associated with the Sterling File Gateway file transfer. Possible values include:
|FG.Arrived File Name||The name of the arrived file involved in the Sterling File Gateway file transfer.|
|FG.Arrived File Status||The status of the arrived file involved in the Sterling File Gateway file transfer. Possible values include:
|FG.Business Process Name||Sterling B2B Integrator business process name.|
|FG.Consumer||The name of the partner who received the arrived file involved in the Sterling File Gateway file transfer.|
|FG.Consumer ContentType||The content type of the file to be delivered.|
|FG.Consumer Mailbox Path||The mailbox path to deliver to a consumer.|
|FG.ConsumerType||The file type the consumer receives.|
|FG.Data Flow ID||The ID of a data flow document associated with a correlation entry or file transfer event.|
|FG.DOCUMENT_ID||Sterling File Gateway Arrived File Document ID|
|FG.Event Code||The Sterling File Gateway equivalent of a message ID.|
|FG.FILE_NAME||Sterling File Gateway Arrived File Name.|
|FG.FILE_SIZE||Sterling File Gateway Arrived File Size.|
|FG.Layer Count||Layers in the file structure.|
|FG.Layer Description||Descriptive string for the layer type.|
|FG.Layer Filename||Name of the file in a layer.|
|FG.Layer Type||Type of layer, such as ZIP, PGP, Text.|
|FG.PayloadName||Name of the file delivered.|
|FG.PROD_ORG_KEY||Sterling File Gateway Producer Org Key.|
|FG.Producer||The name of the partner who created and sent the arrived file involved in the Sterling File Gateway file transfer.|
|FG.Producer Payload||Name of the file produced.|
|FG.Route Count||Number of routes for the arrived file.|
|FG.Routing Channel Template Name||The routing channel template (RCT) defines the structure through which routing occurs.|
|FG.REVIEWED||Sterling File Gateway Reviewed Arrived File|
|FG.ROUTES_REMAIN||Sterling File Gateway Remaining Routes|
|FG.ROUTE_EVENT_KEY||Sterling File Gateway Route Event Key|
|FG.STATE||Sterling File Gateway Arrived File State|
|FG.TIME||Sterling File Gateway Event Time|
|FG.WFID||Sterling File Gateway Arrived File Workflow ID|
|File Agent Name||The unique name for the file agent specified during file agent configuration.|
|File Agent Rule||The rule configured on File Agent that determines which Process to use to submit the file to Sterling Connect:Direct|
|File Agent Trigger File||The file that triggers the rule or the default Process.|
|File Gateway Time||Date and time that events occurred in Sterling File Gateway. Format: yyyy/mm/dd hh:mm:ss.msmsms (UTC +/- hhmm).|
|File Size||Size of file transferred in bytes.
For FTP W3C servers and IIS logs, file size = cs-bytes + sc-bytes (or 0 if neither is available).
For WS_FTP servers, this information is not available.
|From Node||Indicates which server, local or remote, is sending the file. When the value is
P, the server that is initiating the Process is the sender; otherwise, the server that is initiating
the Process is the receiver.
|From Server||Same as From Node.|
|ftpLogRecord||Actual contents of the FTP log record that caused the event to be
For FTP W3C servers and IIS logs, (date time GMT) plus all fields from the log.
|Group ID||SLC Name|
|In Error||Indicates that one or more activities within a Sterling B2B Integrator business
|Is BP||Indicates whether the event is associated with a Sterling B2B Integrator business process.
|Link Fail||Indicates whether a communications error occurred.
|Local Node (P or S)||The server that processed the file.
P = Primary
S = Secondary
|Local Condition Code||The return code of the local Sterling Connect:Direct server.|
|Local Message ID||The message ID of the local Sterling Connect:Direct server.|
|Local Server||The name of the local Sterling Connect:Direct server|
|Log Date/Time||Date and time that the event occurred. Format: yyyy/mm/dd hh:mm:ss.msmsms (UTC
For Sterling File Gateway, this value is the date and time that events were logged in the database.
To see a chronological listing of events, open the Statistics viewer, right-click a column heading, select Manage Columns, and add File Gateway Time to Selected Columns. To sort, right-click the File Gateway Time column.
|Mailbox ID||Mailbox identifier used in Sterling Connect:Enterprise.|
|Message||The server or IBM Sterling Control Center Monitor message ID issued with the event.|
|Message ID||The server or IBM Sterling Control Center Monitor message ID issued with the event. For Sterling File Gateway, Event Code is mapped to Message ID.|
|Message Text||Message description.|
|Minutes Since Last Submit||Number of minutes since the previous submission to the File Agent.|
|MQMFT.The MQ MFT message id||Server or IBM Sterling Control Center Monitor message ID issued with the event.|
|MQMFT.The MQ MFT action type||MQ FTE action type. The values are started, progress, or completed.|
|MQMFT.The action time||Action time. The format is yyyy-mm-ssThh:mm:ss.nnnZ.|
|MQMFT.-call's outcome||The outcome of the call.|
|MQMFT.-call result's error||The resulting error of the call.|
|MQMFT.-call result's outcome||The resulting outcome of the call.|
|MQMFT.-call result's return code||The resulting return code of the call.|
|MQMFT.-call result's stderr output||The call stderr output.|
|MQMFT.-call result's stdout output||The call stdout output.|
|MQMFT.-call result's time||The call result time.|
|MQMFT.-call result's retries||The number of retries for the call.|
|MQMFT.-call command arguments||The call command arguments.|
|MQMFT.-call command name||The call command name.|
|MQMFT.-call command retry count||The call retry count.|
|MQMFT.-call command retry wait||
The call retry wait time.
|MQMFT.-call command successful return code||
The call specification of a successful RC.
|MQMFT.-call command type||
The call command type.
|MQMFT.Destination queue manager||
Name of the destination agent.
Name of the destination agent queue manager.
|MQMFT.Destination bridge URL||The URL if the MQ MFT process bridged the file from MQ to some other protocol (like FTP).|
|MQMFT.Destination's OS arch||
Architecture of the destination agent.
|MQMFT.Destination's OS name||
Name of the destination agent operating system.
|MQMFT.Destination's OS version||
Version of the destination agent operating system.
|MQMFT.MQ MFT identifier for the transfer||
MQ MFT identifier for the file transfer.
|MQMFT.Job name (if provided). Otherwise, MQMFT_transfer.||
Job name (if provided). Otherwise, the value is MQ MFT_transfer.
|MQMFT.User provided metadata||
User metadata. Format is [key1=value1].[key2=value2]...
|MQMFT.Hostname of the originator||
Hostname of the request originator.
|MQMFT.The originator's MQMD userid||
MQMD userid of the originator.
|MQMFT.The originator's userid||
|MQMFT.-postdest call's outcome||The postdest call outcome.|
|MQMFT.-postdest call's error||The postdest call result error.|
|MQMFT.-postdest call result's outcome||The postdest call result outcome.|
|MQMFT.-postdest call result's return code||The postdest call result return code.|
|MQMFT.-postdest call result's stderr output||The postdest call result stderr.|
|MQMFT.-postdest call result's stdout output||The postdest call result stdout.|
|MQMFT.-postdest call result's time||The postdest call result time.|
|MQMFT.-postdest call result's retries||The postdest call result retries.|
|MQMFT.-postdest command arguments||The postdest command arguments.|
|MQMFT.-postdest command name||The postdest command name.|
|MQMFT.-postdest command retry count||The postdest command retry count.|
|MQMFT.-postdest command retry wait||The postdest command retry wait.|
|MQMFT.-postdest command successful return code||The postdest command successful return.|
|MQMFT.-postdest command type||The postdest command type.|
|MQMFT.-postsrc call's outcome||The postsrc call outcome.|
|MQMFT.-postsrc call's error||The postsrc call error.|
|MQMFT.-postsrc call result's outcome||The postsrc call result outcome.|
|MQMFT.-postsrc call result's return code||The postsrc call result return code.|
|MQMFT.-postsrc call result's stderr output||The postsrc call result stderr output.|
|MQMFT.-postsrc call result's stdout output||The postsrc call result stdout output.|
|MQMFT.-postsrc call result's time||The postsrc call result time.|
|MQMFT.-postsrc call result's retries||The postsrc call result retries.|
|MQMFT.-postsrc command arguments||The postsrc command arguments.|
|MQMFT.-postsrc command name||The postsrc command name.|
|MQMFT.-postsrc command retry count||The postsrc command retry count.|
|MQMFT.-postsrc command retry wait||The postsrc command retry wait.|
|MQMFT.-postsrc command successful return code||The postsrc command successful return.|
|MQMFT.-postsrc command type||The postsrc command type.|
|MQMFT.-predest call's outcome||The predest call outcome.|
|MQMFT.-predest call result's error||The predest call result error.|
|MQMFT.-predest call result's outcome||The predest call result outcome.|
|MQMFT.-predest call result's return code||The predest call result return code.|
|MQMFT.-predest call result's stderr output||The predest call result stderr output.|
|MQMFT.-predest call result's stdout output||The predest call result stdout output.|
|MQMFT.-predest call result's time||The predest call result time.|
|MQMFT.-predest call result's retries||The predest call result retries.|
|MQMFT.-predest command name||The predest call command name.|
|MQMFT.-predest command retry count||The predest call result retry count.|
|MQMFT.-predest command retries||The predest call result retry wait.|
|MQMFT.-predest command successful return code||The predest call result successful return.|
|MQMFT.-predest command type||The predest call command type.|
|MQMFT.-presrc call's outcome||The presrc call outcome.|
|MQMFT.-presrc call result's error||The presrc call result error.|
|MQMFT.-presrc call result's outcome||The presrc call result.|
|MQMFT.-presrc call result's return code||The presrc call result return code.|
|MQMFT.-presrc call result's stderr output||The presrc call result stderr output.|
|MQMFT.-presrc call result's stdout output||The presrc call result stdout output.|
|MQMFT.-presrc call result's time||The presrc call result time.|
|MQMFT.-presrc call result's retries||The presrc call result retries.|
|MQMFT.-presrc command arguments||The presrc command arguments.|
|MQMFT.-presrc command name||The presrc command name.|
|MQMFT.-presrc command retry count||The presrc command retry count.|
|MQMFT.-presrc command retry wait||The presrc command retry wait.|
|MQMFT.-presrc command successful return code||The presrc command successful return.|
|MQMFT.-presrc command type||The presrc command type.|
|MQMFT.Source agent queue manager||The source agent queue manager.|
|MQMFT.Source agent name||The source agent name.|
|MQMFT.Source agent bridge URL||The URL if MQ MFT received a file from some other protocol other than MQ (like FTP).|
|MQMFT.Source agent's OS arch||The source agent operating system arch.|
|MQMFT.Source agent's OS name||The source agent operating system name.|
|MQMFT.Source agent's OS version||The source agent version.|
|MQMFT.Statistics actual start time||Statistics actual start time.|
|MQMFT.Statistics number of file failures||Statistics number of file failures.|
|MQMFT.Statistics number of file warnings||Statistics number of file warnings.|
|MQMFT.Statistics retry count||Statistics retry count.|
|MQMFT.rslt code||The result code.|
|MQMFT.MQ MFT msg||MQ MFT message.|
Destination file checksum.
|MQMFT.Destination checksum method||
Destination file checksum method.
The action that is taken if a destination file exists on the destination system. The valid values are as follows:
|MQMFT.Destination last modification date/time||
Last modified date/time of the destination file. The format is yyyy-mm-ssThh:mm:ss.nnnZ.
|MQMFT.Destination queue group id||
Destination queue group ID.
|MQMFT.Destination queue message count||
Count of messages to queue.
|MQMFT.Destination queue message id||
Destination queue message ID.
|MQMFT.Destination queue message length||
Length of message.
|MQMFT.Destination file size||
Destination file size.
|MQMFT.Transfer mode||The transfer mode.|
|MQMFT.Source checksum||The source checksum.|
|MQMFT.Source checksum method||The source checksum method.|
|MQMFT.Source disposition||The source disposition.|
|MQMFT.Source last modified date/time||The source last modified date/time.|
|MQMFT.Source queue group id||The source queue group ID.|
|MQMFT.Source queue message count||The source queue message count.|
|MQMFT.Source queue message id||The source queue message ID.|
|MQMFT.Source queue message length||The source queue message length.|
|MQMFT.Source file size||The source file size.|
|MQMFT.Transfer result code||The transfer result code.|
|MQMFT.Transfer message||The transfer message.|
|MQMFT.Transfer start timeOrig Node||The transfer start time.|
|Name||Same as Process name.|
|Node Name||The name of the server.|
|Node Type||The code that indicates the type of server. The server types are:
Important: The node type for dynamically discovered servers is assigned the first time that IBM Control Center Monitor receives an event from a new type of dynamically discovered server.
|Non-Executing Processes||The number of Processes not being executed, that is, in the Wait, Hold, or Timer queues.|
|Number||Same as Process number.|
|Orig Node||The originating node of a Sterling Connect:Direct, Sterling B2B Integrator, or Global Mailbox process.
For FTP W3C servers, check the cs-username field if available; otherwise, the c-ip field.
For FTP IIS logs, check the cs-username field if available.
|Originating Node/Server||The name of the server or node (PNODE) that initiated the process. For FTP, the submitter ID. User ID of the user that is initiating the work.|
|Other Condition Code||The return code of the remote Sterling Connect:Direct server.|
|Other Message ID||The message ID of the remote Sterling Connect:Direct server.|
|Percent Complete||For Sterling Connect:Direct servers, the percent complete of the file copy or transfer. Relevant only to events with the event type of Process Status.|
|Pnode||The Sterling Connect:Direct primary node.|
|Pnode Acct Info||Accounting information associated with the Sterling Connect:Direct primary node.|
|Process ID||For Sterling File Gateway, the ID
for the business process.
For Sterling Connect:Direct, same as Process number.
|Process Name||The name of the Process or batch ID. (The name of an FTP Process is always
either GET or PUT.)
For FTP W3C servers, this value comes from the cs-method field if available; otherwise, it is the cs-uri field.
For FTP IIS logs, this value comes from the cs-method field.
|Process Name/Batch ID||This key or field maps to the following values:
|Process Number||The number that identifies the process.|
|Queue ID||In Sterling Connect:Direct,
there are 4 processing queues: Exec, Hold, Timer, and Wait.
In Sterling B2B Integrator, there are 10 queues: Q0 through Q9.
|Record Category||Statistics record category. Possible values include:
|Record ID||The record (or statistic ID) used to indicate what Sterling Connect:Direct activities produce associated IBM Sterling Control Center Monitor event types, for example, CH (Change Process) has an Event type of Server Command.|
|Records Read||The number of records read from the source file.|
|Records Written||The number of records written to the destination file.|
|Remote Node/Server||The server or remote node name involved in a Process or file transfer. For Sterling Connect:Direct, the remote node is the SNODE name. For Sterling Connect:Enterprise, the remote node is the recipient mailbox ID.|
|Remote Server||The remote server name.|
|Restart||Indicates if the restart feature of Sterling Connect:Direct is enabled to facilitate recovery should an interruption in data transfer occur.|
|Restart (Y or N)||Indicates if the restart feature of Sterling Connect:Direct is enabled to facilitate recovery should an interruption in data transfer occur.|
|Return Code||Same as condition code.
Return code associated with Process steps and Process ends. Possible values include:
For FTP W3C servers, this comes from the sc-win32-status field if available; else, sc-status field.
For FTP IIS logs, this comes from the sc-win32-status field if available.
|RUS Received||The number of buffers received by the destination server.|
|RUS Sent||The number of buffers sent to the destination file by the sending server.|
|RU Size||In Sterling Connect:Direct, the size of blocks in number of bytes sent in a transmission.|
|Rule ID||The name of the rule triggered by the event.|
|Secure+ Enabled (Y or N)||Indicates if the Secure+ Option feature for a Sterling Connect:Direct file transfer was enabled.|
|Secure Protocol||The protocol, such as TLS or SSL, used in secure Sterling Connect:Direct sessions.|
|Sequence||For Sterling File Gateway, the sequence number.|
|Sequence Number||Sequence number of the statistics record.|
|Server||Actual name of monitored server.|
|Server Alias||Monitored server name used by IBM Sterling Control Center Monitor.|
|Server Data/Metadata 1-10||Server metadata fields for analyzing server information according to the needs of your organization.|
|Server Groups||IBM Sterling Control Center Monitor server group names.|
|Server ID||The name or alias of the server.|
|Server ID/Server Alias||IBM Sterling Control Center Monitor Name/Alias of managed server.|
|Server Name||Name of the managed server.|
|Server Type||The type of server. (Also same as NodeType event element variable.)
Important: The server type for dynamically discovered servers is assigned the first time that IBM Control Center Monitor receives an event from a new type of dynamically discovered server.
|Server Type Name||Type of Server.|
|SESSION.ADAPTER_DISPLAY_ NAME||For a protocol activity, the display name for the Sterling B2B Integrator adaptor.|
|SESSION.ADAPTER_NAME||For a protocol activity, the system name for the Sterling B2B Integrator adaptor.|
|SESSION.ADAPTER_TYPE||For a protocol activity, the display name for the Sterling B2B Integrator adaptor.|
|SESSION.CON_END_TIME||For a protocol activity, the time the Sterling B2B Integrator session connection ended.|
|SESSION.CON_IS_SUCCESS||For a protocol activity, indicates the Sterling B2B Integrator session connection was successful.|
|SESSION.DIS_IS_SUCCESS||For a protocol activity, indicates the Sterling B2B Integrator session disconnection was successful.|
|SESSION.DIS_START_TIME||For a protocol activity, the time the Sterling B2B Integrator session disconnection started.|
|SESSION.END_WFID||For a protocol activity, the workflow ID for the Sterling B2B Integrator session end.|
|SESSION.END_WFSTEP||For a protocol activity, the workflow step for the Sterling B2B Integrator session end.|
|SESSION.ENDPOINT1||Sterling B2B Integrator session end point 1.|
|SESSION.ENDPOINT2||Sterling B2B Integrator session end point 2.|
|SESSION.ENDPORT1||Sterling B2B Integrator session end port 1.|
|SESSION.ENDPORT2||Sterling B2B Integrator session end port 2.|
|Short Msg||The short message text of a message ID. (Also same as shortText event element variable.)|
|Short Text||Message text associated with the Message ID.|
|SI.Adapter Name||Name of the Sterling B2B Integrator adapter.|
|SI.Adapter Type||Type of Sterling B2B Integrator adapter.|
|SI.Document Name||Name of the business document that the business Process works on.|
|SI.Is Put (true/false)||Indicates if a file to a Sterling B2B Integrator mailbox was delivered successfully.|
|SI.Mailbox Path||A storage area path for business documents. The Sterling B2B Integrator mailbox path provides an administrative hierarchy that is easy to manage and understand.|
|SI.Message ID||Message ID of the business information communicated through the business Process.|
|SI.Message Name||Name of the business information communicated through the business Process.|
|SI.Process Data||Data that is accumulated in an XML document about a business process during the life of the process.|
|SI.Session Protocol||Protocol that the adapter handles.|
|SI.Type||For Sterling B2B Integrator server,
indicates the source of the event:
|SLC Flag||Indicates when SLC processing completed.|
|SLC ID||A system-assigned name of the SLC that triggered the event.|
|SLC Identification||A system-assigned name of the SLC that triggered the event.|
|SLC Instance ID||Unique SLC identifier. Includes the SLC name, schedule name, and unique number.|
|SLC Name||The name of the SLC.|
|SLC Source 1||SLC recovery data 1|
|SLC Source Event ID||A system assigned number that identifies the SLC that triggered the event. Used by the system to relate multiple SLC events to the same SLC source.|
|SLC Source Event Time||The time that the event triggering an SLC event occurred.|
|Snode||The secondary Sterling Connect:Direct server involved in the Process. The initiating node in a Process is the Pnode, or primary node.|
|Snode Acct Info||Accounting information associated with the Sterling Connect:Direct secondary node.|
|Source Agent||Source MQ MFT Agent.|
|Source File||For a Sterling Connect:Direct server, the source file name in a Copy. Also the target in a Submit, Run Task, or Run Job Sterling Connect:Direct Process step.
For Sterling Connect:Enterprise, the file name if sent by Sterling Connect:Enterprise or the userid sending the file if received by Sterling Connect:Enterprise.
For FTP, in a PUT, the ID of the user who did the transfer. In a GET, the name of the file received.
For FTP W3C servers, in the case of an inBound source file, this comes from the cs-username field if available; else this comes from the c-ip field.
For FTP W3C servers, in the case of an outBound source file, this comes from the cs-uri-stem field if the FTP command is in the cs-method field; else, this comes from the cs-uri-query field.
For FTP IIS logs, in the case of an inBound source file, this comes from the cs-username field. In the case of an outBound source file, this comes from the cs-uri-stem field.
For Global Mailbox, indicates the file name at the source in a file transfer.
|Standard Compression||Indicates if the standard compression was used while transferring the file.|
|Start Time||The date and time the event started.|
|Start Date/Time||The date and time the event started.|
|Step Name||The Sterling Connect:Direct
Process step name or Sterling B2B Integrator business
Note: This key cannot be used for Sterling Connect:Direct for i5/OS.
|Stop Time||The date and time the event stopped.|
|Stop Date/Time||The date and time the event stopped.|
|Submit Node||The server name that initiated the Process.|
|Submitter/ID||The name or user ID of the person who submitted the Process or Sterling Connect:Enterprise mailbox.|
|SUBMITTER NODE||The name of the node the Process was submitted from.|
|Translation||For Sterling Connect:Direct, the type of translation performed for a Process copy.|
|trapFlag||Indicates when trap operation action completed.|
|User Data 1–4||Metadata fields for analyzing activity in ways unique to your organization.|
|userOpFlag||Indicates when a user operation action completed.|
|WF.ACTIVITYINFO_ID||Business Process Activity Info ID.|
|WF.BASIC_STATUS||Business Process basic status.|
|WF.END_TIME||Business Process end time.|
|WF.NEXT_AI_ID||Business Process next AI ID.|
|WF.NODEEXECUTED||Node where Business Process executed.|
Payload document ID of the Business Process
|WF.SERVICE_NAME||Service name in Business Process.|
|WF.START_TIME||Business Process / Business Process Step start time|
|WF.STEP_ID||Business Process step ID.|
|WF.WFD_ID||Business Process WFD ID.|
|WF.WFD_NAME||Business Process WFD name.|
|WF.WFD_VERSION||Business Process WFD version.|
|WF.WFE_STATUS||Business Process execution status|
|WF.WORKFLOW_ID||Business Process instance ID|
|WFD_NAME||Business Process name|