QALTER(1) Network Queuing Env. 3.3 Last changed: 4-13-98 NNAAMMEE qqaalltteerr - Alters the attributes of one or more NQS requests SSYYNNOOPPSSIISS qqaalltteerr [--cc [nn|ss]] [--cc cc[==_i_n_t_e_r_v_a_l]] [--cc ww[==_i_n_t_e_r_v_a_l]] [--ll _r_e_s_o_u_r_c_e__l_i_s_t]] [--rr [yy|nn]] [--RR] [--RRff] [--uu _u_s_e_r_n_a_m_e] [_r_e_q_u_e_s_t_i_d_s] IIMMPPLLEEMMEENNTTAATTIIOONN IRIX systems UNICOS/mk systems UNICOS systems AIX systems Digital UNIX systems HP-UX systems Solaris systems DDEESSCCRRIIPPTTIIOONN The qqaalltteerr utility alters attributes of specific Network Queuing System (NQS) requests (it can be either queued or executing). You can enter the qqaalltteerr utility from either the command line or from within an NQS request. A request at the local host can be altered by its owner, another user with the proper validation, or an NQS administrator. For more information on user validation, see the NOTES section on the qqssuubb(1) man page. The qqaalltteerr utility accepts the following options: --cc [nn|ss] Indicates whether checkpointing will be performed on the request. If you specify nn, no checkpointing will be performed on the request; if you specify ss, checkpointing will be performed when the NQS server is shut down. --cc cc[==_i_n_t_e_r_v_a_l] Starts checkpointing the request based on the CPU time used by the request. To override the NQS default interval for checkpointing by CPU usage, you can specify the optional interval, in minutes. If you specify an interval, you must use the format ==_i_n_t_e_r_v_a_l and not ==. --cc ww[==_i_n_t_e_r_v_a_l] Starts checkpointing the request based on wall-clock time used by the request. To override the NQS default interval for checkpointing by wall-clock usage, you can specify the optional interval, in minutes. If you specify an interval, you must use the format ==_i_n_t_e_r_v_a_l and not ==. You can enter the cc and ww suboptions together as part of one --cc option. For example, the following --cc option specification is valid: -c c=5,w=20 --ll _r_e_s_o_u_r_c_e__l_i_s_t Specifies changes to resource limits; the _r_e_s_o_u_r_c_e__l_i_s_t is a series of resources, separated by commas, that have the following format: _r_e_s_o_u_r_c_e = _v_a_l_u_e[,_r_e_s_o_u_r_c_e = _v_a_l_u_e,...] The valid resource names and descriptions are as follows: mmpppp__pp Specifies the maximum number of Cray MPP processing elements (PEs) on a Cray MPP system or the maximum number of CPUs on an Origin 64-bit system that are accessible at the local host; this variable is an integer from 0 to 65,536. The alternative form mmaaxxiimmuumm or uunnlliimmiitteedd, or any leading substring thereof, indicates that the maximum value permitted by the user is required. If the total number of Cray MPP PEs or CPUs requested by all processes of the request exceeds the specified limit, an error condition occurs. mmpppp__tt Specifies the maximum per-request CRAY T3D MPP wall-clock residency time or the CRAY T3E MPP connect time for a multiple processing element (PE) application. If the sum of the CRAY T3D MPP wall-clock residency time or the sum of the CRAY T3E MPP connect time for the multiple PE applications exceeds this limit, an error condition occurs, and the batch request is terminated. For more information on the implementation of batch request limits and for a description of the syntax of these per-request time limits, see the Limits subsection of the qqssuubb(1) man page. pp__mmpppp__tt Specifies the maximum per-process CRAY T3D MPP wall-clock residency time or the CRAY T3E MPP connect time for a multiple processing element (PE) application. If the CRAY T3D MPP wall-clock residency time or the CRAY T3E MPP connect time for a multiple PE application process exceeds this limit, an error condition occurs, and the batch request is terminated. For more information on the implementation of batch request limits and for a description of the syntax of these per-process time limits, see the Limits subsection of the qqssuubb(1) man page. sshhmm__ll[[iimmiitt]] Specifies the maximum shared memory size that the job can create. If you try to exceed this limit, an error condition occurs. For more information on the implementation of batch request limits and for a description of the syntax of a per-request shared memory size limit, see the Limits subsection of the qqssuubb(1) man page. sshhmm__ss[[eeggmmeennttss]] Specifies the maximum number of shared memory segments that the job can create. The alternative syntax forms mmaaxxiimmuumm and uunnlliimmiitteedd, or any leading substring thereof, indicate that the maximum value permitted to the user is required. If you try to exceed this limit, an error condition occurs. The owner of a request can increase and decrease the resource limits of requests that reside in a pipe queue. The owner of a request can only decrease the resource limits of requests that reside in a batch queue. An NQS operator or administrator can increase and decrease the resource limits of any request. --rr [yy|nn] Redefines whether the job can be rerun. If you specify yy, the qqaalltteerr utility sets the rerunnable attribute of the job to ttrruuee. If you specify nn, the rerunnable attribute is set to ffaallssee. --RR Redefines whether the job can be restarted normally (with no options). Before you can restart a request, the request must have been checkpointed successfully (that is, a restart file exists). --RRff (UNICOS and UNICOS/mk systems only) Redefines whether the job can be restarted with the force option if files have changed since the last checkpoint. Before you can restart a request, the request must have been checkpointed successfully (that is, a restart file exists). --uu _u_s_e_r_n_a_m_e Specifies the owner of the _r_e_q_u_e_s_t_i_d_s. To alter requests that other users own, you must use this option. _r_e_q_u_e_s_t_i_d_s Specifies a series of NQS request identifiers that have the following format: _s_e_q_u_e_n_c_e-_n_u_m_b_e_r The _s_e_q_u_e_n_c_e-_n_u_m_b_e_r argument is the number assigned to the request at the time of submission. When the qqaalltteerr utility is contained within an NQS job, the _r_e_q_u_e_s_t_i_d is not required. EEXXIITT SSTTAATTUUSS An exit status of 0 indicates normal completion. An exit status of 1 indicates a user error. An exit status of 2 indicates an NQS error. MMEESSSSAAGGEESS The standard error file (ssttddeerrrr) lists explanatory messages for all irregularities. EEXXAAMMPPLLEESS Example 1. The following job script prevents checkpointing for the data retrieval portion of the job, and it later sets checkpointing based on a CPU usage rate of 2 minutes: #QSUB -eo qalter -c n get_data ... qalter -c c=2 process_data ... Example 2. The following line checkpoints request 112233 only during an NQS shutdown: qalter -c s 123 Example 3. The following line checkpoints request 444444 based on the request's CPU and wall-clock usage: qalter -c w=50,c=5 444 Example 4. The following line changes the rerunnable attribute to yyeess for request 445566: qalter -r y 456 Example 5. The following line changes the CRAY T3D MPP resource limits for request 778899: qalter -l mpp_p=32,p_mpp_t=100,mpp_t=1000 789 SSEEEE AALLSSOO qqcchhkkppnntt(1), qqddeell(1), qqlliimmiitt(1), qqmmssgg(1), qqssttaatt(1), qqssuubb(1) for information on batch request submission ccpprr(1) on IRIX 6.4 or later systems for information about checkpoint and restart cchhkkppnntt(2) for information on whether you can checkpoint a request rreessttaarrtt(2) for information on whether you can restart a request in the _U_N_I_C_O_S _S_y_s_t_e_m _C_a_l_l_s _R_e_f_e_r_e_n_c_e _M_a_n_u_a_l, publication SR-2012 iiaa__ffaaiilluurree(3C), iiaa__ssuucccceessss(3C), iiaa__uusseerr(3C) for information about the UNICOS and UNICOS/mk identification and authentication feature in the _U_N_I_C_O_S _S_y_s_t_e_m _L_i_b_r_a_r_i_e_s _R_e_f_e_r_e_n_c_e _M_a_n_u_a_l, publication SR-2080 and the _U_N_I_C_O_S/_m_k _S_y_s_t_e_m _L_i_b_r_a_r_i_e_s _R_e_f_e_r_e_n_c_e _M_a_n_u_a_l, publication SR-2680 nnqqeeiinnffoo(5) for information on the nnqqeeiinnffoo file _N_e_t_w_o_r_k _Q_u_e_u_i_n_g _E_n_v_i_r_o_n_m_e_n_t _U_s_e_r'_s _G_u_i_d_e, publication SG-2148, for information on using NQE and NQS _C_h_e_c_k_p_o_i_n_t _a_n_d _R_e_s_t_a_r_t _O_p_e_r_a_t_i_o_n _G_u_i_d_e, Silicon Graphics publication 007-3236-001 This man page is available only online.