With a shared-use of OCTOPUS, you cannot log in directly to a node and use it interactively, but you can use "interactive batch" function to use it as if it were interactive. Please use it for test execution and debugging purposes.
 

How to use interactive batch

Command and example

By executing the following command, it is possible to use interactively for up to 10 minutes. The job class to be specified in the -q option depends on the type of node to be used interactively.
 

Command example:

$ qlogin -q INT -l elapstim_req=00:10:00 --group=(group-name)

Execution example:

Request 12345.oct submitted to queue: INT.
Waiting for 12345.oct to start.

 
By specifying the qlogin command, you are making a request to the scheduler to "use like interactive". For more information on how the scheduler works, please refer to here.
 

About input options

Following the qlogin command, specify the options at submission time as described in the job script.
Options other than those listed below can be used also, but some of them are not supported. Please refer to this section.

 

-q option

If you want to use interactive batch, specify the interactive job class INT for interactive following -q option.
 

-l option

Following -l option, specify the resource limit to use. Basically, just elapstim_req is fine.
 

--group option

Following --group option, specify group name.(In the case of HPCI users, specify HPCI project ID.)
 

About execution status

When you execute the qlogin command, a request ID will be assigned and you will be in the queue state (waiting state) as in normal batch use. If there is room in the job class "INT", a prompt such as "[user_name@oct-host_name ~]$" will be displayed in about 20 to 30 seconds, and interactive use will be possible.
 
If there are a lot of interactive users and there is not enough space in the job class "INT", the job will not be executed and a message like "Waiting for 12345.oct to start". This indicates that the interactive batch is in the QUE state.
 
It is possible to check the status of the request using qstat or sstat as in normal batch usage.
1 2 3 4

$ sstat RequestID       ReqName  UserName Queue     Pri STT Date(PLANNED START) --------------- -------- -------- -------- ---- --- ------------------- 12345.oct       QLOGIN   w6a020   INT         0 QUE -

1 2 3 4

$ qstat RequestID       ReqName  UserName Queue     Pri STT S   Memory      CPU   Elapse R H M Jobs --------------- -------- -------- -------- ---- --- - -------- -------- -------- - - - ---- 12345.oct       QLOGIN   w6a020   INT         0 RUN -   26.15M     0.02       22 N N N    1

However, when the qlogin command is executed, it will be in a wait state and the prompt will not accept input.
You will need to launch another connection or run the qlogin command with an & (ampersand) in the background.
 

About running the program

As mentioned earlier, when the program is ready for interactive use, a prompt such as "[user name@oct-host name ~]$" will be displayed. After this, you can operate the system as you would in a typical linux environment.
For example, to run the program a.out, you can do the following:

[user_name@oct-host_name ~]$ ./a.out

 

Termination of interactive batches

Execute the following command to terminate the interactive use.

$ logout

Other

NOT supported Input options

Checkpoint-related specifications
Standard output/standard error output file specification
Specify whether to hold or not, and whether to re-run or not.
Staging related specifications
etc.
 

Node-hours consumption

For shared use, node-hours is consumed based on usage.