TWS - Naming Standards

TWS Naming Standards - Jobs and Jobstreams

Having naming standards for jobs and jobstreams in TWS is important for many reasons. To list just a few: the security file that allows permissions to users is kept consistent and simple, searching for jobs and jobstreams in TWS and TWS WebAdmin is simpler, reports and SQL queries in TWS WebAdmin can provide fuller information. This can not only be useful in determining a multitude of statistics for a particular customer, but also provide vital information to the WAS team when calculating the annual fees that are built into budgets.

Names of jobs and jobstreams can be suggested by the customer; however, WAS has final approval of a name - especially if it is a new Area Code and/or Sub-Area Code.

In TWS there are space limitations for jobstreams and jobs. Jobstreams are limited to 16 characters and jobs are limited to 40 characters.

The WAS naming standard is as follows and pertains to jobstreams:

Position # Description
1-2 Area Code
3-4 Sub-Area Code
5-6 Special Codes

The WAS naming standard is as follows and pertains to jobs:

Position # Description
1-2 Area Code
3-4 Sub-Area Code
5-6 Underscore ‘_’

The special codes are used for unique or special runs. This was the old frequency code space.

There should be no exceptions in taking the full five or six characters of a name, even if there isn’t a value for a particular entry.

For example, the Payroll area uses the Area Code of PY and has no Sub-Area Code for their Daily job. The name of the jobstream begins as such: PYPYD_; PYPY_ for jobs.

A second example is the Financial Services Billing group, who use the FS Area Code and BI Sub-Area Code in their Request job. The name of the jobstream begins as such: FSBIR_; jobs with FSBI_.

Finally, a third example is the Shared Financial Systems group, who use the SF Area Code and FN Sub-Area Code in their Daily job that runs during the daytime. The name of the jobstream begins as such: SFFNDD; jobs with SFFND_.

When used, Special Codes can be used as follows:

Code Frequency Description Sub-Frequency Description
A Annual
C CALC runs
D Daily Day
M Monthly
N Nightly
Q Quarterly
R Request
S Semester
W Weekly
Z Twice Yearly




Keywords:TWS, naming standards, run frequency codes   Doc ID:5614
Owner:Rick P.Group:DoIT Workload Automation
Created:2007-03-22 19:00 CDTUpdated:2013-11-27 15:00 CDT
Sites:DoIT Workload Automation, Systems & Network Control Center
Feedback:  1   0