DSXchange

You can certainly create a configuration file that requests fewer nodes than usual, but you can't prevent "them" from starting zillions of jobs each of which will dynamically request that number of nodes from the grid. Some grid management software will let you throttle the number of nodes...

When importing the table definition (at least for a sequential file) you can set the NLS map to NONE. This will prevent every string data type being flagged as Unicode because (for example) the default map being set to UTF-8.

Assuming that you saved/loaded the DataSet table definition (which we all do, right?), it's as easy as performing a "where used" analysis on that table definition.

Have you done a search of DSXchange for "packed decimal"? In those posts you will learn how packed decimal storage is organized, and some code for unpacking the same. You ought never to need to look at them.

At all of the sites where my company is engaged a set of standards is established early in the project, and a peer review process, aided by a checklist, is used for design quality assurance.

Use Head stage for first record(s), Tail stage for last record(s).

Build stage, External Filter stage, just off the top of my head.

It's a hashed file, not a hash file.

Ask about DIS file as well.

What does "special" mean?

Check also that APT_CONFIG_FILE and APT_ORCHHOME are set.

Custom rule sets can be used as often as necessary. It is better, therefore, if some thought has gone into their construction, particularly about handling conditions as generally as possible.

Electrify their keyboards when you want them not to work.

Search DSXchange for "DS.REINDEX"

Question - but there's also IsNotNull()

Players - unless they're section leaders or the conductor.