There is a separate manual for writing server plug-in stages called, from memory, DataStage Plug-In Writer's Guide . It does not ship with the usual set of manuals, but can be requested through your vendor. I would counsel great caution before embarking on this task. Most who have investigated have ...
Of course it's possible, except that you must have a priori knowledge of the metadata to be able to design it! This doesn't just appear out of thin air!
Clearly you did not attend one of the training classes that I ran! If you had a bad experience, do let IBM know. They seem to be quite genuine in wanting to improve the training classes.
There is an Orchestrate Operators manual among the Orchestrate manuals. Your vendor ought to be able to supply you with a set at no cost. They're also handed out on IBM's DataStage EE classes.
Mind over matter. Despite an ageing body, I still play and umpire baseball (and thereby get to think and do other things, outside "work"). And I have a number of strategies to relax, including taking an afternoon out just to play sitar.
Bulk loaders maintain their own log file and their own rejected records file. You can specify where these are. The bulk loader program (bcp in your case) processes the data file only after DataStage has finished writing rows into the data file. Thus you can not capture rows rejected by bcp within th...
If you use a UNIX sort you need to specify the UNIX sort command options that identify the sort key (usually -k, but this might be qualified by other options such as the delimiter option, the sort order option, and so on). On UNIX execute man sort to learn what the options are on your particular UNIX.
You need to make sure that every process (conductor, section leaders, players) associated with the jobs is logged out, is not holding any locks, network resources, file units or other resources.