• Browse
  • Pages
  • News
  • Labels
  • Attachments
  • Bookmarks
  • Advanced
• Log In
• Sign Up
• Help
  • Help Wiki
  • Contact Wiki Admin
• Report an Issue
  • Report a Wiki Space Issue
  • Report a Site Wide Issue

1. Wikis Home
2. Sun Grid Engine 6.2u3
3. …
4. Documentation
5. Administering
6. Using Job Submission Verifiers

• Log In

Using Job Submission Verifiers

• Attachments:1
• Added by Anonymous, last edited by Sandra.Konta on Feb 25, 2009

Comment:

Searching Sun Grid Engine 6.2u3 Documentation Optional Features Reference Library Release Notes Patch Matrices Man Pages Troubleshooting Error Messages FAQ Glossary Printing Options Previous Releases Sun Grid Engine 6.2u2 Sun Grid Engine 6.2 Sun N1 Grid Engine 6.1 N1 Grid Engine 6.0 Sun ONE Grid Engine - Enterprise Edition 5.3 Expert Advice Expert Advice by Topic Expert Advice by Type Community Contributing to the Community Get Answers Give Feedback Using the Wiki Additional Resources Index へようこそ (Japanese)

Grid Engine Home > Administering >

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.

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.
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.
JSV Verification Process	Learn about how the Sun Grid Engine system executes JSVs.
Configuring JSVs	Learn how to configure JSVs.
JSV Communication Protocol	Learn about the communication protocol used by JSV instances to communicate with a client process and/or the master daemon.

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 Leave a comment below

Learn More For more on this topic, check out the following resources: Expert Advice – Video: Introduction to Grid Engine Expert Advice – White Paper: Beginner's Guide to Sun Grid Engine (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

Labels parameters

Labels

Enter labels to add to this page:

 

Looking for a label? Just start typing.

Children (5)

  Hide Children  |  View in Hierarchy

Understanding the Differences Between Client JSVs and Server JSVs
Configuring JSVs
Writing JSV Scripts
JSV Communication Protocol
JSV Verification Process

Sign up or Log in to add a comment or watch this page.