1.60 August 19, Sergey Satskiy Group lists for GET2/READ/READ2 for NS 4.23.0 2015 1.61 October 26, Sergey Satskiy Adding a note about the command synopsis. 2015 1.62 11, 2016 Sergey Satskiy Adding information the feature for NS ‘scope’ 4.25.0 1.63 September 16, Sergey Satskiy GET2/READ2 allowed any_aff together with 2016 prioritized_aff for NS 4.27.0 1.64 September 27, Sergey Satskiy Fixed RECO output description 2016 1.65 October 13, Sergey Satskiy REDO and REREAD commands for NS 4.28.0 2016 1.66 December 13, Sergey Satskiy affinity and group for NS 4.29.0 ‘-‘ 2016 1.67 May 11, 2017 Sergey Satskiy Added GET2 output parameters (submitter_notif_host and submitter_notif_port) for NS 4.30.0 1.68 November 17, Sergey Satskiy Addig need_progress_msg parameter for 2017 SST2/WST2/LISTEN/SUBMIT commands; adding need_stolen for LISTEN command. Job change notification format changes are described. The changes are for NS-4.31.0. 1.69 November 20, Sergey Satskiy Adding need_progress_msg parameter for STATUS2 2017 command for NS 4.31.0 1.70 November 23, Sergey Satskiy Adding new DUMP options for NS 4.42.0 2018 NetSchedule Protocol This document describes the NetSchedule server protocol in detail. Overview The NetSchedule protocol is based on human readable strings exchanged over a TCP/IP connection. An exchange unit is a line which is ended by a carriage return character. The figure below shows the overall structure of the protocol. Protocol Structure A session of communication with a NetSchedule server starts with opening a TCP/IP connection.
1.60 August 19, 2015 Sergey Satskiy Group lists for GET2/READ/READ2 for NS 4.23.0 1.61 October 26, 2015 Sergey Satskiy Adding a note about the command synopsis. 1.62 11, 2016 Sergey Satskiy Adding information the ‘scope’ feature for NS 4.25.0 1.63 September 16, 2016 Sergey Satskiy GET2/READ2 allowed any_aff together with prioritized_aff for NS 4.27.0 1.64 September 27, 2016 Sergey Satskiy Fixed RECO output description 1.65 October 13, 2016 Sergey Satskiy REDO and REREAD commands for NS 4.28.0 1.66 December 13, 2016 Sergey Satskiy ‘-‘ affinity and group for NS 4.29.0 1.67 May 11, 2017 Sergey Satskiy Added GET2 output parameters (submitter_notif_host and submitter_notif_port) for NS 4.30.0 1.68 November 17, 2017 Sergey Satskiy Addig need_progress_msg parameter for SST2/WST2/LISTEN/SUBMIT commands; adding need_stolen for LISTEN command. Job change notification format changes are described. The changes are for NS-4.31.0. 1.69 November 20, 2017 Sergey Satskiy Adding need_progress_msg parameter for STATUS2 command for NS 4.31.0 1.70 November 23, 2018 Sergey Satskiy Adding new DUMP options for NS 4.42.0 NetSchedule Protocol This document describes the NetSchedule server protocol in detail. Overview The NetSchedule protocol is based on human readable strings exchanged over a TCP/IP connection. An exchange unit is a line which is ended by a carriage return character. The figure below shows the overall structure of the protocol. Protocol Structure A session of communication with a NetSchedule server starts with opening a TCP/IP connection.
NetSchedule%20Command%20Reference.docx