University of Kentucky Computing Center                         Page 1
          July, 1979
                                   REMOTE USERS' GUIDE
             This guide  is intended  for use as  a standard  of policy  for the
          operations  and management  staff for  remote users  connected to  the
          University  of Kentucky  node  of  the Kentucky  Educational  Computer
          Network (KECNET).
             For  additional  information,   remote  users   may  refer  to  the
          University of Kentucky Computing Center (UKCC) Users' Guide.
          I.  Job Submission
             Jobs are divided into two basic categories: setup and non-setup.  A
          setup job requires  either operator intervention or  some other setup:
          tape mounts, disk mounts,  or replies to disk or tape data sets.   All
          other jobs are non-setup.
             The format of the standard JOB card is:
               //jobname JOB 1234-56789,username
          where 1234-56789  is the 10-character  account number assigned  to the
          user for accounting  purposes.   The "username" field may be  up to 20
          characters, and, if it contains blanks or special characters,  must be
          enclosed in quotes; e.g., 'IM A USER'.   See the UKCC Users' Guide for
          JOB card parameters.
             The following card deck setup is recommended for job submission:
                     /*CLASS     (if desired)
                     //  standard  JOB  card
                     /*ROUTE     (if desired)
                     /*PASSWORD  (if required)
                     /*JOBPARM   (if desired)
                     /*MESSAGE   (if required)
             If present,  //PROCLIB  and //JOBLIB cards should  follow the above
          cards, but must precede the first EXEC card.
             Production  type jobs  for  the remote  site may  be  run with  the
          approval of the UKCC Manager of Operations.
               A.  Classes
                  There  are four  classes  of jobs  that  the  remote user  may
               request: A, X, Z, and Q.   The default class is Z, unless /*SETUP
               cards are present; then, the default class is A.   Class X may be
               used  for fast  turnaround  of one-step  jobs  using  any of  the
               following procedures  with no DD cards  other than SYSIN DD  * or
               SYSIN DD DATA:
                    ASMGC     COBFC     COBUCG    FORTGG    LIST     SPASM
                    ASMGCG    COBFCG    FORTGC    GO        PCAP     SPITBOL
          University of Kentucky Computing Center                         Page 2
          July, 1979
                                   REMOTE USERS' GUIDE
                    ASSIST    COBUC     FORTGCG   LISP      PLC      WATFIV
                  A more up-to-date list of eligible  procedures may be found in
               section of  the UKCC Users' Guide or  in announcements in
               The Kentucky Register newsletter.
                  If you use COBUCLG, COBFCLG, ASMGCLG, or FORTGCLG,  but do not
               use any special  features of the linkage editor (you  do not have
               any linkedit DD cards or control cards),   you may be able to use
               the  corresponding  -CG  suffix procedure  instead  of  the  -CLG
               suffix.   If you use IBM's Assembler F, you may wish to switch to
               Assembler G, which is usually faster and cheaper.
                  Please note that Class X jobs cannot punch cards.   Class Z is
               the default class for jobs requiring  no operator setup;  Class A
               is  for  jobs needing  operator  action  of some  kind  (replies,
               mounts,  any special  handling).   Class Q jobs  require more CPU
               time and/or  greater region  size;  these jobs  are run  when the
               Operations staff  determines that system resources  are available
               (see sections I.B and I.C of this guide).  Class may be specified
               via the CLASS= parameter on the JOB card or on the /*CLASS card.
                  The /*CLASS card has the following form:
                         cc1      cc10
                          |        |
                          /*CLASS  x
               where x is the job class.  The /*CLASS card must be placed before
               the JOB card.   If both a CLASS= parameter and a /*CLASS card are
               present, the CLASS= parameter value is used.
               B.  Region Requirements
                  The default region size  for Class A and Z jobs  is 134K;  for
               Class X, it is 150K.   Class A and Z jobs, however, may specify a
               region of up to 1024K,  but jobs specifying over 268K may receive
               slower turnaround.  Jobs with a region size greater than or equal
               to 512K automatically become Class Q jobs, which are run when the
               Operations staff determines that  system resources are available.
               In any case,  the region size will affect the priority of the job
               (smaller region size = higher priority).
               C.  CPU Time
                  The default  CPU time limit  for any  job is ten  seconds.   A
               different limit may be specified with  the TIME= parameter on the
               JOB  card or  JOBPARM  card.   Jobs  with  estimated time  limits
               greater than or equal to  four minutes automatically become Class
               Q jobs,   and are run when  the Operations staff  determines that
               system resources  are available.    Jobs exceeding  the CPU  time
               limit are  cancelled automatically.    Note that  the time  limit
               affects  the priority  of  the job  (lower  time  limit =  higher
          University of Kentucky Computing Center                         Page 3
          July, 1979
                                   REMOTE USERS' GUIDE
               D.  Line and Card Limits
                  The default line limit is 10,000 lines and the default punched
               card limit is 2,000 cards.  A different limit may be specified on
               the JOBPARM  card.   Jobs exceeding  the limit will  be cancelled
               automatically.   Jobs generating  over 20,000 lines will  be held
               when finished executing and must be released by the remote site.
                  Jobs which print more than 125,000 lines must be arranged with
               the UKCC Manager of Operations or the Operations Supervisor,  and
               should be broken into segments.
               E.  Non-Rerunable Jobs
                  It will be  assumed that any job may be  rerun (restarted)  at
               any time during its execution,  unless a reply has been given for
               a disk data set,  or RD=NORERUN is specified on the JOB card,  or
               NR or NORERUN is specified on the JOBPARM card.
               F.  Replies to Disks
                  Any job  requiring a reply to  a date-protected data  set must
               include a MESSAGE card:
                    /*MESSAGE  --->  PLEASE REPLY 'U' TO dsname
               (See note  in section  I.H of  this guide.)    The job  must also
               specify CLASS=A on the JOB card.
               G.  Disk and Tape Mounts
                  Any job  requiring more than  one disk  mount per job  step or
               three tape drives per job step must be approved by the Manager of
               Operations at the UKCC.   All jobs  requiring tape or disk mounts
               must use /*SETUP cards as described below:
                         COLUMN        FIELD
                          1-7         /*SETUP
                          8-9         Blanks
                         10-71        Keywords and values,
                                      separated by commas
                         72-80        Ignored
               The format of the SETUP keywords is as follows:
                 1. /*SETUP  TAPE=volume
                    /*SETUP  TAPE=(volume,ringin/out,label,track)
                    where "volume" is the volume serial number of the tape;
                          "ringin/out" specifies RINGIN or RINGOUT
                                       (the default is RINGOUT);
                          "label" specifies SL (Standard Labels) or NL
                                  (the default is SL);
                          "track" specifies 9 or 7 (default is 9-track).
          University of Kentucky Computing Center                         Page 4
          July, 1979
                                   REMOTE USERS' GUIDE
                 NOTE:   Operators  are instructed not to  put a ring in  a tape
                 unless it is specified in the SETUP card.
                    Some SETUP card examples:
                    /*SETUP  TAPE=ABC123           No ring, 9-track, labeled
                    /*SETUP  TAPE=(ABC123,RINGIN)  Ringin, 9-track, labeled
                    /*SETUP  TAPE=(ABC123,,NL)     No ring, 9-track, no label
                 2. /*SETUP  DISK=(volume,unit)
                    where  "volume" is the volume serial number of the disk,
                    and    "unit" specifies either 2314 or 3330, the type of
                                  the disk.
                    /*SETUP  DISK=(DEF456,2314)
                    NOTE:  Currently there are no 3330 type drives available
                           for mounting of offline 3330 disk packs.
                 3. /*SETUP  DSN=dsname  or
                    /*SETUP  DSN=(dsname,ringin/out)
                    where  "dsname" is the name of a catalogued data set,
                    and    "ringin/out" specifies RINGIN or RINGOUT
                                        (the default is RINGOUT),
                    the latter  parameter being  only for  catalogued tape  data
                    sets,  as the system will determine the volume serial number
                    and type of device from the  catalog.   It is suggested that
                    data sets residing on tape not be catalogued.
                  Possible  error messages  pertaining  to  SETUP cards  are  as
                  "ILLEGAL SET  CARD" indicates  a syntax  error in  the /*SETUP
                  "DISK DATA  SET" indicates "ringin/out"  specified in  the DSN
                     parameters,   but the  data  set is  catalogued  on a  disk
                  "ILLEGAL DSN" indicates  a syntax error in  the "dsname" field
                     of the DSN parameters, or an uncatalogued data set name.
                  "CATALOG  ERROR" and  "CATALOG ERROR  (I/O)" indicate  special
                     conditions which should be brought  to the attention of the
                     UKCC Systems staff.
                  The user may supply as many  /*SETUP cards as necessary to run
               the job.   Please note that /*SETUP  cards must have this format,
               contrary to  the documentation in  the HASP Remote  Users' Guide.
               The SETUP card may be eliminated in  the future.   The use of the
               SETUP card will  not force the job  to be held,  contrary  to the
               documentation in the HASP Remote Users' Guide.
               H.  Plot Jobs
          University of Kentucky Computing Center                         Page 5
          July, 1979
                                   REMOTE USERS' GUIDE
                  Remote users  have the ability to  run plot jobs.    The plots
               will be done, charged to the user, and mailed to the remote user.
               The user must supply /*MESSAGE and /*SETUP cards as follows:
                    /*MESSAGE  ----> PLOT JOB
                    /*MESSAGE  ----> PLEASE CHARGE PLOT TO: account-number
                    /*MESSAGE  ----> PLEASE SEND PLOTTED OUTPUT TO:
                    /*MESSAGE  ----> user's name
                    /*MESSAGE  ----> user's address
                    /*MESSAGE  ----> IF PROBLEMS, CALL user's name and number
                    /*SETUP  TAPE=(SCRTCH,RINGIN)
                  NOTE:   MSGLEVEL=(0,0) should not be coded on the JOB card, as
               it suppresses printing of MESSAGE cards on the listing.
                  If a  job has plotted output  produced at the  LOCAL (CENTRAL)
               site, it must also have printed output routed to the LOCAL site.
               I.  Punched Output
                  If the remote site does not have a card punch,  punched output
               for  jobs from  that site  will be  punched at  the UK  Computing
               Center.   Unless a MESSAGE card  indicates the disposition of the
               punched output,   the punched  output will  either be  deleted or
               thrown away.   Please indicate building number, etc.,  since most
               of the  material will be  sent via UPS  (in which case  P.O.  box
               number is not useful).   An example  of a message for disposition
               of punched output is:
                    /*MESSAGE  ----> PLEASE SEND TO:
                    /*MESSAGE  ----> user's name
                    /*MESSAGE  ----> user's address
                  Users who  punch large  amounts of  data at  the UKCC  will be
               charged extra for the cost of the cards.
                  If a  job has punched output  produced at the  LOCAL (CENTRAL)
               site,  it must also have printed output routed to the LOCAL site.
               (See note in section I.H of this guide.)
               J.   /*JOBPARM and /*OUTPUT cards
                  The JOBPARM card from  HASP 4.0 (a version of HASP  used by VS
               release 1 users) will be supported by the UKCC as follows:
                                COLUMN        FIELD
                                 1-9         /*JOBPARM
                                10-11        Blank
                                12-71        Keywords and Values,
                                             separated by commas
                                72-80        Ignored
          University of Kentucky Computing Center                         Page 6
          July, 1979
                                   REMOTE USERS' GUIDE
                         Keywords                 Description
                         CARDS=cccccc             Estimated card count
                             C=cccccc             Numeric value (0-999999)
                         COPIES=nnn               Job copy count
                              N=nnn               Numeric value (1-255)
                         FORMS=ffff               Job forms
                             F=ffff               Alphameric value
                                                  (1-4 characters)
                         LINECT=kkk               Lines per page
                              K=kkk               Numeric value (0-255)
                         LINES=llll               Estimated line count
                             L=llll               Numeric value (0-9999)
                         NOLOG                    No HASP job log
                             J                    (No value should be
                         NORERUN                  Non-rerunable job
                              NR                  (No value should be
                         SPACE                    Ignore carriage control
                             S                    (No value should be
                         TIME=(mmmm,ss)           Estimated execution time
                            T=(mmmm,ss)           Numeric value (0-279620)
                         WASTE                    Recognize all carriage
                             W                    (No value should be
                  Any JOBPARM  values will  supersede the  parameter on  the JOB
               card or on any previous JOBPARM card.   The user may have as many
               JOBPARM cards as  necessary.   If an error is  encountered on the
               JOBPARM card,  the  message BAD JOBPARM CARD will  follow the bad
               card and the job will be deleted.   The user should remember that
               the NOLOG,  SPACE,  and WASTE  parameters override each other and
               the last one appearing will be used.
                  The TIME keyword parameter may be  used to limit or extend the
               CPU time  for the  job.   Use  of the  TIME parameter  allows the
               specification of time limits in minutes and seconds.   The number
               of minutes must be less than 1440;  the number of seconds must be
          University of Kentucky Computing Center                         Page 7
          July, 1979
                                   REMOTE USERS' GUIDE
               less than 60.    If the CPU time  is given in minutes  only,  the
               parentheses are not necessary; i.e., TIME=2.   If the CPU time is
               given  in  seconds only,   then  the  parentheses and  the  comma
               indicating  the absence  of  minutes  must be  specified;   i.e.,
               TIME=(,30).   For more information  regarding the TIME parameter,
               see section of the UKCC Users' Guide.
                  The /*OUTPUT card  was not adapted from HASP 4.0;   it is only
               logged on the UKCC operator's console.   Thus,  the /*OUTPUT card
               is not supported from remote sites.
               K.  Special Print Forms
                  If an  entire job is  to be printed  on special forms  such as
               2-part  paper,  the  user may  request  "job forms"  by coding  a
               1-to-4-digit number as  the fifth job accounting  subparameter on
               the JOB card, i.e.,
                    //jobname  JOB  (acct-number,,,,1234),name
               or by specifying a forms code on the JOBPARM card:
                    /*JOBPARM  FORMS=1234
                  If only one data set of a job is to be printed (or punched) on
               special forms, the SYSOUT card should appear as follows:
                    //ddname  DD  SYSOUT=(J,,ffff)  for printed output, or
                    //ddname  DD  SYSOUT=(K,,ffff)  for punched output
               where ffff  is a 1-to-4-digit forms  code.   The entire  job will
               print (punch)  ______ for the SYSOUT=J (K)  data set and then the
               job will go to the special forms queue to print (punch)  only the
               special forms data sets.
                  In order for this to work  properly,  the remote operator must
               periodically issue  the $DF command  to display the  forms queue,
               and then issue:
                    /*$TRMn.PR1,F=ffff (or .PU1 for the punch)
               to cause  that specific data set  to print (punch)   (see section
               IV.D of this  guide).   Users must arrange for  their own special
               forms when output is printed (punched) at the UKCC.
          II.  Tape and Disk Data Sets
               A.  Tapes
                  All  users  are  requested  to  use  standard  labeled  tapes.
               Unlabeled tapes  should be  copied to  standard labeled  tapes as
               soon as possible, preferably within two days.  Tape volume serial
          University of Kentucky Computing Center                         Page 8
          July, 1979
                                   REMOTE USERS' GUIDE
               numbers  should  consist  of  three  letters  followed  by  three
               numbers,  the first three letters being the assigned tape identi-
               fication code  for that particular  remote site.    The preferred
               tape density is 6250 bpi,  except in the case where the tape will
               also  be  used  at another  computer  installation  which  cannot
               process 6250 bpi tapes.  UKCC users will generally not be allowed
               to use these tapes without special permission from the Manager of
               Operations,  and  remote users will  generally be allowed  to use
               only these  tapes.   It is suggested  that data sets  residing on
               tape not be catalogued.
                  Remote users are  allowed to use 17000 series  tapes for input
               only.   These tapes are maintained by  the UKCC staff and contain
               information  of  general  interest.   For  example,   tape  17018
               contains  UKCC documentation  which is  voluminous and/or  infre-
               quently printed.  Tape 17207 contains DECsystem-10 documentation,
               which users  may prefer  to print on  the IBM  high-speed printer
               rather than at a low-speed  terminal.   Other examples are census
               data, Kentucky voter registration, and the ERIC bibliography.
                  New tapes to  be retained in the UKCC tape  library for remote
               sites should  be sent  to the Operations  Supervisor at  the UKCC
               along with a cover letter indicating owner, volume serial number,
               density, and label type.   Unlabeled tapes,  non-full-size reels,
               seven-track tapes, or O.S.   standard labeled tapes not beginning
               with the assigned prefix may be  retained at the UKCC only tempo-
               rarily;   the user  must make  arrangements to  copy these  tapes
                  Remote users already having tapes at  the UKCC not meeting the
               above  requirements should  make immediate  arrangements to  have
               these tapes  copied and  returned to  the user.    All new  tapes
               submitted  to the  UKCC  should have  thin  self-loading "EL  II"
               cartridges.    Each tape  must have  three  external labels:    a
               completed UKCC (blue and white) label and two white labels boldly
               lettered (in black)  with the tape's name.   One of the two white
               labels should be affixed neatly (trimmed  to fit)  to the edge of
               the container.    Each of these label  types is available  at the
               UKCC Data Center  (remote users may obtain labels  by calling the
               Operations Supervisor on duty--the labels will be sent).
                  Do not use box (permanent adhesive)   labels on tapes or their
               containers.    The external  label  must  accurately reflect  the
               recording characteristics used; i.e., whether it is labeled (OS),
               what the volume serial number is,  recording density,  and number
               of tracks.  If a tape is to be labeled (i.e., labeled by OS), the
               tape is held aside until a tape label  job is run.   If a tape is
               not to be  labeled (i.e.,  it already  is labeled or it  is to be
               used unlabeled  and already  contains data),   then the  external
               labels are checked  for accuracy.   The tape is  then placed with
               the other tapes for that remote site.  When placing labels on the
               self-loading cartridges,  please do not  place the label over the
               tape  entrance on  the  cartridge.   If  you  have  a problem  or
               question, contact a member of the UKCC Operations staff.
          University of Kentucky Computing Center                         Page 9
          July, 1979
                                   REMOTE USERS' GUIDE
               B.  Disks
                  Users may  rent online  3330 disk  space at  the UK  Computing
               Center for a monthly charge of $2.00 per cylinder.   One cylinder
               (19 tracks) can hold about 3,000 card images (1 1/2 boxes).   The
               actual amount of storage needed will vary with the RECFM,  LRECL,
               and BLKSIZE.
                  The UK Computing  Center backs up (copies)  rental  disks on a
               regular basis;  these usually extend  back six months.   However,
               users should be  sure to back up important  data sets themselves.
               Normally,   security is  not  a  concern beyond  keeping  backups
               current.   When an  archive data set is written  on online rental
               disk, a high expiration date can be set by coding:
                  Then nobody,  not  even the owner,  can write on  the data set
               without an operator reply (See section I.F of this guide).   This
               is useful if you are very concerned about preventing over-writing
               of data, and you do not plan to update the data.
                  A rental disk data  set must reside on a disk  designated as a
               rental disk.  Currently these are UKC001, DPC002, DPC003, UKC004,
               UKC005, and UKC006.   The DSNAME must have an identifying prefix;
               e.g.,  'UKU. XYZ01'.   The first  qualifier (UKU)  identifies the
               institution and  the second ( XYZ01)  identifies  the department.
               The  prefix is  assigned when  a  project number  for disk  space
               rental is set up.   The rest of the name is assigned by the user;
               e.g., 'UKU. XYZ01.MYDATA'.
                  When you allocate  a permanent data set,   specify UNIT=RENTAL
               and omit the VOL=SER.  This allows the operating system to assign
               a rental volume with enough free space to hold the data set.  The
               actual volume selected will be listed in the allocation messages.
               If you are allocating a temporary data set (just for the duration
               of the job),   specify UNIT=SYSDA,  and a scratch  volume will be
               assigned.   Permanent  user data  sets on  scratch disks  will be
               erased without warning.
                  All user data sets should be catalogued.  The user can use the
               LITLMAP and MAPRENT utilities to monitor disk usage.   The remote
               site is responsible  for making sure that only  desired data sets
               are left on the disk.   MAPRENT output may be verified on a daily
                  The remote user may purchase (or already own) a 2314 disk pack
               for low volume-of-usage disk data sets,  which will be considered
               offline storage to be mounted at the user's request.   Currently,
               3330 disks may not be mounted.
                  Disk packs  belonging to  remote users to  be retained  at the
               UKCC must be approved by the  UKCC Manager of Operations.   Other
          University of Kentucky Computing Center                        Page 10
          July, 1979
                                   REMOTE USERS' GUIDE
               input data  or output  media should be  arranged with  either the
               Operations Supervisor or the Manager of Operations at the UKCC.
          III.  Private Procedure Libraries
             A private  procedure library may be  created for the  remote site's
          use.  The user may then specify use of this procedure library by means
          of the //PROCLIB DD card, a regular DD card like the JOBLIB card which
          follows the JOB  card but precedes the EXEC card.    It is recommended
          that this be  called remoteindex.PROCLIB;  it will reside  on a rental
          disk and may be maintained by the remote site as a regular PDS.
          IV.  Operation
               A.  Hours
                  The UKCC  usually has  the network  running continuously  from
               8:00 AM  to 7:00 AM Eastern  time,  Monday through  Friday.   The
               network runs until 9:00  PM on Saturday and from noon  to 1:00 AM
               on Sundays.   Holiday schedules appear  in The Kentucky Register.
               The operators  will attempt to  inform remote users  of scheduled
               IPL's which will cause a disruption in service, but these are not
               always foreseen;  for example, a quick and brief thunderstorm may
               terminate service  for all  users suddenly.    The Systems  Group
               system maintenance  may be scheduled  in the evening  after 12:00
               midnight,  or in the morning before  7:00 AM,  but the group will
               attempt  to  inform  remote  sites   several  hours  in  advance.
               Engineering activity  may occur in the  morning prior to  7:00 AM
               (advance notification is attempted).
               B.  Connection
                  If you  connect to the  network via a  dialup line and  get no
               answer or busy signal,  or get  no response to initial connection
               if you  are at  a remote  site,  contact  the UKCC  Computer Room
               Supervisor on duty at the time.   The supervisor will insure that
               the lines are started  and data sets are in AUTO.    If you think
               that your line or modem is not working, first check with the UKCC
               to make certain that the 370 is running.   If it is running, then
               contact   Darrel  Brooks   at   the   University  of   Louisville
               (502-588-6123) about your problem.
               C.  Routing Printed and Punched Output
                  There  are four  basic types  of locations  to which  computer
               output may be routed:
                  1.  The Computer Room in McVey Hall at the UK Computing Center
                      LOCAL (CENTRAL) site.
                  2.  The Hands-on Printer in room 111 McVey Hall (HOT).
                  3.  A CJS user's virtual card reader (VM370).
                  4.  HASP remote job entry sites (REMOTEm).
          University of Kentucky Computing Center                        Page 11
          July, 1979
                                   REMOTE USERS' GUIDE
                  Generally, printed and/or punched output can be routed between
               any of these sites,  with  certain restrictions.   These restric-
               tions include the following:
                  a.  If a  job has  punched or plotted  output produced  at the
                      LOCAL site, it must also have printed output routed to the
                      LOCAL site.
                  b.  Hands-on jobs may not have punched output.
                  c.  Hands-on output is limited to 1600 lines.
                  d.  CJS output  is limited to 1600  lines and 2000  vards.  (A
                      vard is a virtual card.)
                  e.  Some HASP remote sites do not have punches.
                  f.  Jobs routed to CJS users or HASP remotes must have /*SETUP
                      cards for tape or disk mounts.
                  Print and/or  punch routing is  determined by HASP  before the
               job goes into execution.   A job can have HASP ROUTE cards, or it
               can take a default routing;  Hands-on  jobs print on the Hands-on
               Printer.   HASP remote  jobs have output directed  to that remote
                  Printed  and/or  punched  output is  normally  routed  to  the
               submitting site.  If the site does not have a punch,  the punched
               output will  appear at  the UKCC  site unless  the job's  punched
               output  has been  routed elsewhere  via  the /*ROUTE  card or  $R
               operator command.   To route a job to be printed (or punched)  at
               the UKCC, specify:
                         Columns       Descriptions
                           1-7         /*ROUTE
                          10-14        PRINT (or PUNCH)
                          16-23        LOCAL
               and place the above card(s) immediately after the JOB card.
                  The format of the HASP ROUTE card is:
                    /*ROUTE  type  dest  (VMuserid)
                  type       is  either PRINT  or PUNCH,   depending on  whether
                             printed or punched  output is to be  routed.   This
                             field must begin in column 10.
                  dest       is the  destination for the  output.   This  may be
                             LOCAL (CENTRAL)  for the Computer  Room at UK,  HOT
                             for the Hands-on Printer, VM370 for a CJS user,  or
                             REMOTEm for the HASP remote having number m.   This
                             field must begin in column 16.
          University of Kentucky Computing Center                        Page 12
          July, 1979
                                   REMOTE USERS' GUIDE
                  VMuserid   is the id of the CJS user whose virtual card reader
                             will receive the output.   This field must begin in
                             column 24 and  is used  only if  VM370 is  coded in
                             column 16.
                  When  jobs are  routed to  sites  other than  the user's  own,
               arrangements should be made in advance  for handling of the job's
               output.   A message  can be sent alerting the remote  site to the
               expected output by using a HASP  Display Message card.   The card
               has the format:
                    /*$DMm,'message text'
               where m is the remote number and  message text is the message you
               wish to convey.  The Display Message cards will not be recognized
               by HASP if they are within a job,  so they should be the first or
               only cards read on the card reader.    These cards can be read on
               the Hands-on Reader at  the UKCC or a reader at  a remote site as
               long as they are not stacked behind  other cards.   If the job is
               to be turned in  at the UKCC Data Center and  the Display Message
               cards must be read  on with the job,  then the  message cards and
               the job should  be given to the Operations Supervisor  on duty in
               the UKCC Computer Room,  room 59 McVey Hall,  to ensure that they
               are the first cards on the reader.
                  An example of a job routed to a remote site would be:
                    /*$DM2,'A. PROGRAMMER IS SENDING YOU A JOB'
                    /*$DM2,'WITH JOBNAME JOB1'
                    /*$DM2,'PLEASE SAVE THE OUTPUT FOR'
                    /*$DM2,'JOHN USER'
                    //JOB1   JOB card
                    /*ROUTE  PRINT REMOTE2
                    /*PASSWORD     password
                              rest of job
                  If a UKrunid card is used,  it should follow the message cards
               and precede the JOB card.
                  If  remote users  wish to  have  their output  printed at  the
               University of Kentucky Computing Center so that a staff member at
               UK can pick  up the output,  the  user should use a  V UKrunid in
               conjunction with HASP ROUTE cards.  The V UKrunid card causes the
               job to have  a V run number.    The Operations staff at  the UKCC
               will then file the output for the staff member to pick up.   Jobs
               which run  with V run  numbers are  not allowed replies  and must
               have /*SETUP cards for any mounts.  The default limits are 10,000
               lines and 2,000 cards (these may  be changed with JOBPARM cards).
               The format of the V UKrunid card is:
                    /*PRIORITY     ,V-xnnn
          University of Kentucky Computing Center                        Page 13
          July, 1979
                                   REMOTE USERS' GUIDE
               where x is a  digit from 1 to 9 and nnn is  any other three digit
               number.   It is desirable that x not  be zero in order to distin-
               guish the run  id from those generated internally  by HASP.   The
               comma before the V must be in column 16.
                  The CENTRAL HASP ROUTE cards are:
                    /*ROUTE  PRINT LOCAL
                    /*ROUTE  PUNCH LOCAL
                  These cards must follow the JOB card.   PRINT begins in column
               10 and LOCAL begins in column 16.
                  An example of a  job routed to the UKCC with  a V UKrunid card
                    /*PRIORITY     ,V-1000
                    //  standard  JOB  card
                    /*PASSWORD     password
                    /*ROUTE  PRINT LOCAL
                    /*ROUTE  PUNCH LOCAL
                         rest of job
                  A remote user may wish to route  printed output to a CJS user.
               In the  following example,  the printed  output is routed  to the
               VMuserid UCC101 for a UKCC staff  member to read.   CJS output is
               limited to 1600 lines.
                    //  standard  JOB  card
                    /*PASSWORD     password
                    /*ROUTE  PRINT VM370   UCC101
                    /*ROUTE  PUNCH VM370   UCC101
                          rest of job
               D.  Special Forms
                  At the beginning  of the day,  if  the remote site has  a real
               console (e.g.,   a 3780  only has  a simulated  console with  the
               reader and printer), the following card should be read on:
               which will allow  only standard forms to print.   The remote site
               operator should periodically check the forms queue by issuing:
               and if the queue is not empty, set the printer at some convenient
               time to that particular forms code by issuing:
          University of Kentucky Computing Center                        Page 14
          July, 1979
                                   REMOTE USERS' GUIDE
               where 1234  is the  indicated forms code.   When the  printing is
               finished,  the remote site operator should  set the forms back to
               F=S as above.  Note that 'n' above is the remote number.
               E.  Job Scheduling
                  An ordinary  HASP system  schedules all  jobs,  regardless  of
               submitting  source,  in  priority order  based on  time and  line
               estimates.    The priority  scheme used  by the  UKCC forces  job
               selection for execution by priority within submission group.  The
               priority of a  job is dependent on CPU  time limit specification,
               largest region size, and nondeferred/deferred account pay status.
               For example, two jobs from Remote 'X', one being 1 minute,  134K,
               the other 2 minutes, 134K, will run in that order.   Each time an
               initiator is ready for new work,  it selects the highest priority
               job  from the  next source  in  a "round"  group selection  list.
               Every odd time,   a UKCC job is selected;  every  even time,  the
               initiator tries to select a job from a remote site, starting in a
               cyclic fashion  with the  next remote  after the  last one  used.
               For example,  if Remote 3 was selected from last,  it will try to
               select from Remote 4, then 5, then 6, etc., then back to Remote 1
               again,  and so on until it finds a job or wraps completely around
               the list (no Remote jobs to run).   If all remote sites have jobs
               to be run,  it will select in  this fashion:  UKCC job,  Remote 1
               job,  UKCC job,   Remote 2 job,  ...   and back  to the beginning
               F.  Transmission Errors
                  If an  unusual number  of transmission  errors occur  within a
               small amount of time,  the UKCC operators have been instructed to
               restart the line,   which will disconnect a dialup  line.   If an
               unusual number of errors occur, the operators will drain the line
               completely and wait  for the remote site to call  and discuss the
               problem.   Otherwise,  they  have been instructed to  ignore most
               errors, which are usually due to noise on the transmission lines,
               a common but unavoidable problem.    Additionally,  if the remote
               site calls the UKCC operator and  requests it,  the operator will
               restart  the line.    This  restarting  operation usually  resyn-
               chronizes  the computer  and  remote terminal  back  to a  normal
               sequence.   The operator  or remote site may contact  a member of
               the UKCC Systems Group in case of unusual problems.   If problems
               persist,   the remote  site should  contact the  UKCC Manager  of
               G.  Signing On and Off
                  Remote sites using  leased lines are permanently  connected to
               the computer system, whereas if a dialup line is used, the remote
               site must identify itself with a SIGNON card:
                         Column       Field
                          1-8        /*SIGNON
          University of Kentucky Computing Center                        Page 15
          July, 1979
                                   REMOTE USERS' GUIDE
                         16-23       REMOTEnn
                         25-32       line password, if any
                                     (otherwise blank)
                  We currently do not assign a password to the dialup lines, but
               may do so in  the future.   If a line password  is assigned,  the
               remote site will be contacted  in advance.   Remotes using dialup
               lines must remember to read on  the /*SIGNOFF card when finished.
               If the SIGNOFF card is not read,   the telephone at the UKCC will
               not disconnect until  an operator at the UKCC  restarts or drains
               the line.   This prevents anyone else from using the line,  as it
               will be busy.
          V.  Communication
             Official communications and  policy changes must be  mailed between
          sites.   Newsletters,  Users' Guide updates,   and UK Computing Center
          Memoranda are to be considered official communications.   The consoles
          are  a  convenience  intended for  minor  communications  and  problem
          solving  only.    During slack  or  extremely  busy periods  the  UKCC
          operators may not see messages from remote sites, so if no response is
          given within a few minutes, please resort to a telephone call.
          VI.  Consulting
             If a remote user  has a problem with JCL or use  of a program,  the
          consultant at the site should be  contacted about the problem.   If no
          one at the site is able to help the user,  the UKCC Consultants may be
          able to help;  call Lavine Thrailkill or Wanda Spisak at 606-258-2914.
          For problems of a system nature (for example, an abend in a compiler),
          contact a member of the UKCC Systems Group at the same number.
          VII.  Sending Jobs and/or Tapes via UPS
             A job which prints over 10,000  lines  may tie up a remote site for
          some time.   If desired,  the job  may be routed locally for printing,
          and sent via UPS  to the remote  site.   Punched or plotted output and
          magnetic tapes  will be  sent the same  way.   /*MESSAGE  cards should
          accompany such jobs whose printed/punched/plotted output is to be sent
          in this manner, giving means of transport,  name,  address,  and phone
          number.   Contact  the UKCC Operations  Supervisor directly to  have a
          tape sent.   The UKCC will pay charges,  and send via UPS the same day
          if possible.    UPS picks  up packages daily  around 10:00  AM Eastern