Other Naming Rules

1. Transaction Code

Transaction codes are written as follows.

Online transaction code
Classification	Description
Composition	Operation name (uppercase)
Application example	SSMP1001A001
Basic principle	- Transaction codes are written to match the operation name (uppercase). One transaction code is mapped to one service operation.

2. Log File

The basic service log for transaction logging is stored in the service log table and can be checked through the web admin screen. Service logs are also created as separate log files, and log files are created for each online instance.

Online logging
Classification	Description
Composition	Online log prefix + node name + instance name
Application example	app_DFT1_online1.log
Basic principle	It consists of the online log prefix, node name, and instance name. Use `log` as the file extension. The location of the log file is as follows: $\{log configuration location}/online

3. Batch Job ID

Batch job IDs are written as follows.

Batch job ID
Classification	Description
Composition	JOB ID
Application example	JSmpAccountTaxSum JSmpTotalProc
Basic principle	- The batch job ID has the same composition as the JOB ID.

4. Batch Log File

Batch log file names are written as follows. Business developers do not need to create them directly; they are created per creation timestamp when the batch is executed.

Batch logging
Classification	Description
Composition	Job ID + _ + 14-digit timestamp
Application example	JSmpAccountTaxSumb_20180806165255.log JSmpTotalProc_20180807102740.log
Basic principle	It consists of the JOB ID and the execution timestamp (14 digits). Use `log` as the file extension. The location of the log file is as follows: $\{log configuration location}/batch/$\{batch application name}

SWLab Bankware Global