[Grid Engine Home|Home] > [Administering] >
{excerpt}
h1. !administering.png! Using Job Submission Verifiers
Job Submission Verifiers (JSVs) allow users and administrators to define rules that determine which jobs are allowed to enter into a cluster and which jobs should be rejected immediately. A JSV is a script or binary that can be used to verify, modify, or reject a job during the time of job submission or on the master host.
The following are examples of how an administrator might use JSVs:
* To verify that a user has write access to certain file systems.
* To make sure that jobs do not contain certain resource requests, such as memory resource requests ({{h_vmem}} or {{h_data}}).
* To add resource requests to a job that the submitting user may not know are necessary in the cluster.
* To attach a user's job to a specific project or queue to ensure that cluster usage is accounted for correctly.
* To inform a user about certain job details like queue allocation, account name, parallel environment, total number of tasks per node, and other job requests.
A verification can be performed by a *client JSV* instance at the time of job submission, by a *server JSV* instance on the master host, or by a combination client JSVs and server JSVs. In general, client JSVs should meet your cluster's needs. See below for more information on what client JSVs and server JSVs have to offer.
h3. Job Submission Verifier Topics
||Topic||Description||
|[Understanding the Differences Between Client JSVs and Server JSVs]|Before you get started, it is important that you learn the differences between client JSVs and server JSVs.|
|{anchor:scripts}[Writing JSV Scripts]|Learn how different programming languages can impact the performance of your cluster, about JSV script-based functions, and how to write JSV scripts.|
|{anchor:verification}[JSV Verification Process]|Learn about how the Sun Grid Engine system executes JSVs.|
|{anchor:configuration}[Configuring JSVs]|Learn how to configure JSVs.|
|{anchor:communication}[JSV Communication Protocol]|Learn about the communication protocol used by JSV instances to communicate with a client process and/or the master daemon.|
{excerpt}
{section}
{column:width=50%}
{panel:borderStyle=solid|borderColor=#5382a1|titleBGColor=#5382a1|bgColor=#ffffff}
*Participate*
Have a best practice to share? Questions? Suggestions? Comments?
* [Add a page] to the Expert Advice section
* [Ask the community] a question
* Send the writing team an [email|mailto:gridengine-writers@sun.com]
* Leave a comment below
{panel}
{column}
{column:width=50%}
{panel:borderStyle=solid|borderColor=#5382a1|titleBGColor=#5382a1|bgColor=#ffffff}
*Learn More*
For more on this topic, check out the following resources:
* Expert Advice -- [Video: Introduction to Grid Engine|http://www.youtube.com/watch?v=0JBsMitNnQ8]
* Expert Advice -- [White Paper: Beginner's Guide to Sun Grid Engine|http://www.sun.com/offers/details/Sun_Grid_Engine_62_install_and_config.html]
(If you are not already registered with sun.com, you must fill out a
quick registration form to gain access to this white paper.)
* Expert Advice -- [Podcast: Towards Cloud Computing with Sun Grid Engine 6.2|http://blogs.sun.com/HPC/entry/podcast_towards_cloud_computing_with]
{panel}
{column}
{section}
{excerpt}
h1. !administering.png! Using Job Submission Verifiers
Job Submission Verifiers (JSVs) allow users and administrators to define rules that determine which jobs are allowed to enter into a cluster and which jobs should be rejected immediately. A JSV is a script or binary that can be used to verify, modify, or reject a job during the time of job submission or on the master host.
The following are examples of how an administrator might use JSVs:
* To verify that a user has write access to certain file systems.
* To make sure that jobs do not contain certain resource requests, such as memory resource requests ({{h_vmem}} or {{h_data}}).
* To add resource requests to a job that the submitting user may not know are necessary in the cluster.
* To attach a user's job to a specific project or queue to ensure that cluster usage is accounted for correctly.
* To inform a user about certain job details like queue allocation, account name, parallel environment, total number of tasks per node, and other job requests.
A verification can be performed by a *client JSV* instance at the time of job submission, by a *server JSV* instance on the master host, or by a combination client JSVs and server JSVs. In general, client JSVs should meet your cluster's needs. See below for more information on what client JSVs and server JSVs have to offer.
h3. Job Submission Verifier Topics
||Topic||Description||
|[Understanding the Differences Between Client JSVs and Server JSVs]|Before you get started, it is important that you learn the differences between client JSVs and server JSVs.|
|{anchor:scripts}[Writing JSV Scripts]|Learn how different programming languages can impact the performance of your cluster, about JSV script-based functions, and how to write JSV scripts.|
|{anchor:verification}[JSV Verification Process]|Learn about how the Sun Grid Engine system executes JSVs.|
|{anchor:configuration}[Configuring JSVs]|Learn how to configure JSVs.|
|{anchor:communication}[JSV Communication Protocol]|Learn about the communication protocol used by JSV instances to communicate with a client process and/or the master daemon.|
{excerpt}
{section}
{column:width=50%}
{panel:borderStyle=solid|borderColor=#5382a1|titleBGColor=#5382a1|bgColor=#ffffff}
*Participate*
Have a best practice to share? Questions? Suggestions? Comments?
* [Add a page] to the Expert Advice section
* [Ask the community] a question
* Send the writing team an [email|mailto:gridengine-writers@sun.com]
* Leave a comment below
{panel}
{column}
{column:width=50%}
{panel:borderStyle=solid|borderColor=#5382a1|titleBGColor=#5382a1|bgColor=#ffffff}
*Learn More*
For more on this topic, check out the following resources:
* Expert Advice -- [Video: Introduction to Grid Engine|http://www.youtube.com/watch?v=0JBsMitNnQ8]
* Expert Advice -- [White Paper: Beginner's Guide to Sun Grid Engine|http://www.sun.com/offers/details/Sun_Grid_Engine_62_install_and_config.html]
(If you are not already registered with sun.com, you must fill out a
quick registration form to gain access to this white paper.)
* Expert Advice -- [Podcast: Towards Cloud Computing with Sun Grid Engine 6.2|http://blogs.sun.com/HPC/entry/podcast_towards_cloud_computing_with]
{panel}
{column}
{section}