> Kirk Wolf wrote:> Pity there is no z/OS port of bash that supports > local > spawn, which is important in many cases.
Pipes and spawn go against z/OS fundamental philosophy. Spock's famous Star Trek saying summed it up best. The needs of the business outweigh the needs of the employee. Pipes and spawn are designed around being selfish. They can suck the life out of a machine and I've seen it happen when compiling programs in MVS Unix. Talk to your sysprog for methods that are more z/OS appropriate. Pipes, spawn and many of selfish Unix facilities rely on knowledge programmers don't have. Business priorities (programmers are low priority unless solving a critical problem). Hardware / software configuration (Single real machine with multiple lpars). These facilities exist in z/OS but they are heavily controlled. z/OS has admins who make these decisioins and change the system according to business requirements (e.g. Compiles in batch to limit concurrent compiles). Unix has admins but there isn't much they can change. Instead, every programmer makes decisions that may conflict with others. I suspect admins were happy when the PKILL command was added. It allowed them to kill all tasks that matched the pkill text. Unix programmers on z/OS should be trained to avoid their instincts. In fact, they should program in Cobol for a few months to get rid of their Unix habits that don't apply to z/OS. If you don't have access to those features, you are more likely to ask what is the correct way to do it is and often find out z/OS already does it for you. Regards, Jon.
