Tom Parker
|
by Tom Parker
Since September, MIGS (the MASnet/Internet Gateway Server) has used the Network Queueing Environment (NQE) rather than MASnet, the old NCAR
local network, for job submission to NCAR Cray and SGI hosts.
A number of users have experienced account problems as a result of the
change to NQE. Below, we recommend ways to facilitate job submission
and solve common problems with the new NQE method used by MIGS.
Problem 1: "No account authorization at transaction peer"
If you get the error message "No account authorization at transaction peer," do the following:
- Check your .rhosts file on the NCAR host machine (Crays, SGIs):
- The file must contain the line:
migs.ucar.edu
- It must not be writable by anyone other than you. (If it is,
UNICOS and NQE will not honor it, as a security
precaution.) To ensure the file is writable only by you, type:
chmod 600 .rhosts
- Check your .rhosts file on the divisional system:
- The file must contain the line:
migs.ucar.edu masgw
- It must not be writable by anyone other than the user (see
#1, above).
- Remove any .nqshosts file on the NCAR host.
Problem 2: "Invalid project number"
If you get the error message "Invalid project number," do the following:
- Update your project number entry in the MIGS database.
This entry is settable either by you or your divisional
systems administrator; see the MIGS User
Guide for instructions on setting your project number entry
or,
- Specify the project number explicitly with:
#QSUB -A xxxxxxxx
in
your job script. (This overrides whatever is in the
MIGS database).
Note: Users' .ntwkparms files are no longer used by MIGS. This
has
ramifications if you have both Climate Simulation Laboratory (CSL) and community
project numbers and use MIGS verbs such as oujob.
We recommend option 2 (specifying the project number
explicitly in the job script) for users with both kinds of
accounts.
Problem 3: "Batchname" command fails
- The batchname command no longer works. Use:
#QSUB -o
output_filename
in your job script instead.
|
