rh._.exports({"0":[[" ","bldcomms"]],"1":[[" ","bldcomms"," ","The ","bldcomms"," utility communicates from a build step back to the PBEM or a build server. You can run ","bldcomms"," from the Windows, UNIX, or USS command-line prompts, or from MVS batch."," ","To run ","bldcomms"," issue this command:"," ","bldcomms monitormessage <node> <port> \"<content of message>\""," ","where:"," ","Parameter"," ","Description"," ","\"<content of message>\""," ","Messages have two possible formats:"," ","I=<step num> T=<timestamp> M=<qprefix messageq>"," ","R=<num> I=<step num> T=<timestamp>"," ","where:"," ","<step num>"," is the step number that identifies the BRD step that this message relates to (in templates use the symbol %DMSTEP.)."," ","<timestamp>"," is the timestamp, in the format ","yyyyttddhhmmssuuuuuu",", that is constructed by the PBEM as part of template processing and is checked to ensure a match. You can also use always matches."," ","<qprefix messageq>"," is as follows:"," ","’","q","’ is a quotation character."," ","’","prefix’","is the prefix of a message. The last letter of the prefix message describes the severity of the message. E and W are always delivered to the build server, other levels (T, I, and D) are not."," ","’message’"," is the content of the message."," ","For example:"," ","\"M="," ","<num>"," is the return code (an integer)."," ","<","node>"," ","Specifies the node number of the application expecting the message, typically the PBEM. In a template use the symbol %DMPBEMNODE."," ","<port>"," ","Specifies a randomly generated port number used by the PBEM to communicate with its started tasks. In a template use the symbol %DMPBEMPORT."]],"id":"397"})