GLOBUS_GRAM_CLIENT_JOB_INFO_S(3)

πŸ“¦
version 14.7 Β· 6 versions
, in epel 10, fedora 43, fedora 44, ubuntu resolute, ubuntu stonking

✨ NAME ✨

globus_gram_client_job_info_s β€” the extensible job information structure, bestie πŸ’–


🌸 SYNOPSIS 🌸

#include <globus_gram_client.h>

πŸ’… Data Fields πŸ’…

globus_hashtable_t extensions
char * job_contact
int job_state
int protocol_error_code

πŸ’– Detailed Description πŸ’–

Okay so this is the extensible job information structure, and yes she is exactly what she sounds like ✨

The globus_gram_client_job_info_t data type is the whole point here β€” she's the girl who carries protocol extensions around alongside all the standard job status info that comes bundled in the GRAM2 protocol. Think of her as the friend who shows up with the main character info plus the extra receipts 🫢

So basically this structure holds everything that gets returned in job state callbacks, plus a whole hash table of extension entries. And those extension entries? They contain #globus_gram_protocol_extension_t name-value pairs. iykyk πŸ’…


πŸŽ€ Field Documentation πŸŽ€

πŸ¦‹ globus_hashtable_t globus_gram_client_job_info_s::extensions

Table of extension values. Literally the little treasure chest of extras, no cap ✨

🌸 char* globus_gram_client_job_info_s::job_contact

GRAM Job Contact String β€” the contact info for your job, like her @ handle but for GRAM πŸ’–

⭐ int globus_gram_client_job_info_s::job_state

GRAM Job State β€” where your job is at emotionally, fr fr

πŸ”₯ int globus_gram_client_job_info_s::protocol_error_code

GRAM Error Code β€” the number that tells you what went wrong, and honestly sometimes it's giving πŸ’€


πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for globus_gram_client from the source code. Not me writing it by hand, the robot did it, and she ate πŸ€–βœ¨


okay that's the whole page bestie, you understood it, I'm so proud of you πŸ₯ΉπŸ’œ

This was globus_gram_client Version 14.7 β€” mwah, go forth and read your job info πŸ’…πŸŽ€