DataStage folder structure

The following is a screen shot showing an example of the folder structure used the project.


General conventions used:

Folders beginning with zz are in the development environment only. They will not be migrated to SIT, UAT or PROD.
zz has been used for-->
1)Load profile data
2)Copy production data to development
3)Sandbox for individual developers play jobs
4)Obsolete to temporarily hold jobs before they are deleted
-->Top level folders are not numbered.
1)_COMMON is used for common objects. The underscore ensures it lists at the top,
2)Each run stream has top level folder, in uppercase. Eg, ALFA, BPS, CMPF.
--->Second level folders are numbered based on the high level processing step.
00 Sequences. Only sequences called from autosys are included here. Sub-sequences (if any) are included in the appropriate sub-category.
10 Preprocess.
20 Extract and Validate
30 Load Staging
40 Transform
50 Target Delta
60 Load GDW
70 Reserved (possibly for Reconciliation)
80 Post process
90 Utility (not yet in use)
99 Obsolete. Used to mark jobs that have already been promoted to production as obsolete. A job will be moved to this folder, with a change history comment as to why it is made obsolete. It will then be promoted to production, and in so doing will move the job out of the original folder.

Note that not all folders will necessarily contain objects.
-->Third level folders are as required.
-->A similar folder structure is used for Shared containers and Routines.