AGENDA
In most cases, a simple deletion of all references to stderr in existing subsystem code would suffice for this change in MONITOR design. The method deemed best by the cognizant engineer for each individual subsystem will be acceptable. The goals are:
The EXEC/PCP script is being implemented in a form that involves calling subsystems via a csh script wrapper. In most cases, this subsystem script need not do very much beyond invoking the subsystem executable program with appropriate command line parameters, but these parameters need to be set up so that the names used are consistent with environment variables provided by the main scripts (i.e., EXEC/PCP). There is also a need to control path information and perhaps other standard operating mode declarations.
Since most subsystem cognizant engineers have not yet seen the EXEC/PCP definitions of supplied environment variables, J. White has stated that he expects to support each Cog E in the writing of the wrapper script. It is also expected that some additional environment variables will be needed, and he will add them as he is informed of such needs.
Since the subsystem scripts comprise an interface between EXEC or PCP with individual subsystems, it is highly desirable for an interface definition to be prepared in each case that supplies all information needed to assure consistency; this would include signoff lines for cognizant individuals involved in the interface. A new SIS format is probably required, and might take the form of a simple listing of the script along with parameter definitions. The EXEC/PCP SDS will document all environment variables, so to a large extent, simply referencing the version of the EXEC/PCP SDS may suffice in the SIS's.
The memo also details file naming schemes, use of a single NAMELIST file to provide multiple NAMELIST input, and other such considerations. Team members are requested to become familiar with the contents so that they can be discussed more fully at next week's meeting.