This task allows a user to emulate into another Pseudo City Code (PCC) within a session. After emulation, the user in effect becomes a user in that Pseudo City and can manipulate data for the Pseudo City. This task is typically used by Service Bureau Agents to perform duties for multiple Pseudo City Code accounts.
Transaction Name:
SessionEmulation_1_0
Can any other transactions perform this same task?
This is the only transaction available to emulate another Pseudo City.
Can this task be performed in a sessionless environment?
This task can only be performed in a sessioned environment.
Are the request and response identical on both the Apollo and Galileo systems?
The request and response for this task are identical on both the Apollo and Galileo systems.
Industry-specific knowledge required to understand this task in terms of the specific business process.
None.
Special limits or distinct restrictions to the input data that may not be readily apparent.
None.
Request:
Unless otherwise specified, use ALL CAPS in any request data.
For a Terminal Security Emulation request, a <SessionMods> data record is required with an <EmulatePCC> element. <EmulatePCC> must contain the Pseudo City Code (PCC) and a duty code to be emulated. The most common duty code “AG” for Agent. Checks are done to ensure the user can emulate, the user can emulate into the requested PCC, and the user can emulate as the requested duty code.
Prerequisite tasks:
The user must be signed onto a Host system and be authorized for emulation to use this Transaction.
Terminal Command:
To emulate a PCC, you must first sign on to a service bureau and then submit the emulation terminal transaction. The format of this transaction is as follows:
|
Terminal Request |
Terminal Response |
|
SEM/AG/PCC |
A confirmation that you have emulated the specified PCC. |
Note: The PCC above should be the PCC that you want to emulate.
Expected response:
The response from a Terminal Security Emulation request will be a <SessionInfo> data record with a <SecurityMessage> element. <SecurityMessage> contains text to indicate if the request was successful or, if an error occurred, what the error was.
Error and warning responses:
The most prevalent errors will be for non-authorization based on either the Pseudo City or duty code requested.
Follow-on requests:
There are no follow-on requests for this task.
|
<SessionMods> |
Terminal Equivalents: Apollo: SEM/GK4/AG
|
|
|
Ordering |
KLR |
Min/Max |
KLR Name |
|
|
GSEM |
1 – 1 |
<EmulatePCC> |
|
<SessionInfo> |
|
|
|
Ordering |
KLR |
Min/Max |
KLR Name |
|
|
GSMG |
1 – 1 |
<SecurityMessage> |