globus_gra..._job_state(3)
π globus_gram_protocol_job_state β GRAM Job States π
okay bestie, welcome to the Library Functions Manual β¨ this is the page for globus_gram_protocol_job_state, aka the GRAM Job States and it's literally just the whole vibe dictionary for "what is my job doing rn" π
π NAME π
globus_gram_protocol_job_state β GRAM Job States
- GRAM Job States.
(yeah they said it twice, iconic of them, no notes π«Ά)
β¨ SYNOPSIS β¨
Enumerations
enum globus_gram_protocol_job_state_t {
GLOBUS_GRAM_PROTOCOL_JOB_STATE_PENDING =1,
GLOBUS_GRAM_PROTOCOL_JOB_STATE_ACTIVE =2,
GLOBUS_GRAM_PROTOCOL_JOB_STATE_FAILED =4,
GLOBUS_GRAM_PROTOCOL_JOB_STATE_DONE =8,
GLOBUS_GRAM_PROTOCOL_JOB_STATE_SUSPENDED =16,
GLOBUS_GRAM_PROTOCOL_JOB_STATE_UNSUBMITTED =32,
GLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_IN =64,
GLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_OUT =128,
GLOBUS_GRAM_PROTOCOL_JOB_STATE_ALL =0xFFFFF }
πΈ DETAILED DESCRIPTION πΈ
GRAM Job States. periodt π
so globus_gram_protocol_job_state_t is holding all the tea about the current state of the job as known by the job manager. every time the state changes, the Job Manager sends that update out to all registered clients β like a group chat notification but for your job's whole life π¦
and a client can also just. ask. π via the status request, if it wants the info on demand.
π₯ ENUMERATION TYPE DOCUMENTATION π₯
enum globus_gram_protocol_job_state_t
GRAM Job States
Enumerator
GLOBUS_GRAM_PROTOCOL_JOB_STATE_PENDINGβ the job is just sitting there waiting for resources to become available so it can actually run. it's giving "on read" energy πGLOBUS_GRAM_PROTOCOL_JOB_STATE_ACTIVEβ yay!! the job got its resources and the application is executing. main character moment, fr fr β¨GLOBUS_GRAM_PROTOCOL_JOB_STATE_FAILEDβ the job terminated before completion because of an error, a user-triggered cancel, or a system-triggered cancel. rip πGLOBUS_GRAM_PROTOCOL_JOB_STATE_DONEβ the job completed successfully. ate and left no crumbs πGLOBUS_GRAM_PROTOCOL_JOB_STATE_SUSPENDEDβ the job has been suspended. and heads up: resources that were allocated for this job may have been released due to some scheduler-specific reason. so like, don't assume they're still yours π«ΆGLOBUS_GRAM_PROTOCOL_JOB_STATE_UNSUBMITTEDβ the job has not been submitted to the scheduler yet, because it's waiting on the reception of theGLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_COMMIT_REQUESTsignal from a client. it's pending approval bestie, we don't move till we get the signal πGLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_INβ the job manager is staging in files to run the job. bringing the supplies in π¦β¨GLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_OUTβ the job manager is staging out files generated by the job. cleaning up and carrying the results out π§ΊπGLOBUS_GRAM_PROTOCOL_JOB_STATE_ALLβ a mask of all job states. literally all of them, the whole squad π
π AUTHOR π
Generated automatically by Doxygen for globus_gram_protocol from the source code. (not a human writing this, just doxygen doing its lil thing, and honestly? respect π«‘)
aaaand that's the page!! π this was globus_gram_protocol Version 13.6 β tysm for reading, go check your job states, mwah πππ¦
π¦ where this page comes from
- fedora 43: globus-gram-protocol-doc 13.6-10.fc43 Β· Apache-2.0
- fedora 44: globus-gram-protocol-doc 13.6-11.fc44 Β· Apache-2.0
- ubuntu resolute: libglobus-gram-protocol-doc 13.6-3build2 Β· Apache-2.0
- ubuntu stonking: libglobus-gram-protocol-doc 13.6-4 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms