Bert Swope
Standards
Standard practices help you and other understand your work. This can be very important when working on large teams, working across team boundaries, or when large complex sets of process and objects may be involved. When you consider the importance of naming convention, when coupled with standard practice, the benefit should be obvious, but often practice doesn’t execute or document their conventions. So, these standard naming conventions may help when none exist or you need to assemble your own naming conventions.
<<SomeIdentifier >> = should be replaced with appropriate information
- Sequence Object Naming Conventions
| Entity | Convention |
| Master Control Sequence (parent) | Master_<<Application>>_ <<Application Job Stream Name>>_Seq |
| Sequence | <<Application>>_<<job_Name>>_Seq |
- Sequence Stage Naming Conventions
| Entity | Convention |
| End Loop | EL__<<PrimaryFunction>> |
| Error Handler | EH_<<PrimaryFunction>> |
| Execute Command | EC_<<PrimaryFunction>> |
| Job Activity | Job_<<PrimaryFunction>> |
| Nested Condition | NC_<<PrimaryFunction>> |
| Notify | Notify_<<PrimaryFunction>> |
| Routine Activity | Rtn_<<PrimaryFunction>> |
| Sequence Links (messages) | Msg_<<Number or Description>> |
| Sequence Links (Non-messages) | Lnk_<<Number or Description>> |
| Sequencer | Seqr_<<Number or Description>> |
| Sequencer (All) | SeqAll_<<Identifier>> |
| Sequencer (Any) | SeqAny_<<Identifier>> |
| Start Loop | SL__<<PrimaryFunction>> |
| Terminator Activity | TA__<<PrimaryFunction>> |
| User Variables | UV__<<PrimaryPurpose>> |
| Wait For File | WFF__<<PrimaryFunction>> |
1 Comment