HETGroup

Contact Info	Name	Phone Number	E-Mail
Technical	Bev Freeman

 

 

 

• HETGroup instructions (PDF) – keyboard settings etc…
• Shortened version:
  • Open a Putty session to “atlas2.hetgroup.org” (user/password above)
  • Alternatively: SSH into [email protected] via a terminal emulator (like if you’re on a Mac)
  • In the command line, enter “menu” (start the Integrow/Genesis menu)
    
  • Enter W (WolffPack Development)
      
  • Enter fnancier in Direct command (FINANCIER)
    
  • POOF! You’re online…
    

This is getting kinda big, so here’s an abbreviated index:

• Other notes (Natural / Linux commands)
• Graphical notes (WinSCP and local Windows editors)
• Directory Structures/Job submission
• Job List

Details, details…

• • Other notes:
    • UUNLOCK
      If you try to run a process that aborts, or if you get disconnected while you’re in a NATURAL object, you’ll end up with things being locked and not accessible. You have to know where they’re locked up – get into that library and do a direct command of UUNLOCK. It will give you a place to enter what you want to unlock in that library (fortunately, you can unlock everything that might be locked up with a * wildcard).
    • Predict (You need to be in via option D (WolffPack DBA function) if you are going to regen an AF or DDM!)
      • To get into Predict, you enter NATURAL and select library SYSDIC. You will get a list of objects. Hit ESCAPE and you’ll see the old PREDICT entrance screen. Hit ENTER, and you’ll get the Predict menu.
      • If you happen to get an object locked up in Predict, you have to recover it using the Predict command menu – option “S” for Special functions, and then “R” for Recover, then another “R” for Recover and the file name (I think that you do have to know what’s locked up for this one).
      • Regen AF (ADABAS File) – we can do this Regen, but not an initial file (we can’t do Natural Security which needs to be done on an initial gen….)
    • Editor (Natural editor)
      • One of the more useful commands is “

      L DIR

      ” which allows use to see some internal Natual “notes” about the complied object. Most useful is the cross-reference list to external subroutines. This can be used to determine if there are subroutines which are not found (the cross reference name will be blank.
    • SYSMAIN (Library utility)
      To copy Natural objects (programs, subprograms, maps, copycode, etc.) from library to library (WolffPack ‘standard operating’ procedure is to release from a “temp” library), at the Natural menu, go to Services/SYSMAIN. You can copy Natural obhects using the SYSMAIN menu.
    • SYSOBJH (Object unload)
      • To unload Natural objects (programs, subprograms, maps, copycode, etc.) from a library, there’s a special version of Natural “D – WolffPack DBA function” (as opposed to W – WolffPack Development) which sets up special work files. After getting into Natural via “D”, go to the Direct Command line and issue the command “SYSOBJH”.

      Notes:

      • Leave the defaults on the first two screens, on the third screen where the “options” are, just leave everything as is. On the fourth, leave the choice as “Do not use parameters”. On the screen where you designate a library and object names, be sure to BLANK OUT the Error numbers, otherwise it will unload some weird stuff having to do with error messages.
      • When you are finished with the SYSOBJH, make sure you select No on the ‘Do you want to continue the unload function?’ Screen and press Enter.
      • If you do not press enter, the last buffer is not written to the work file
      • The dataset is in your home directory (ex:/home/hartwigd) and is called cmwkf01.dat You can rename this to whatever you need.

      ADABAS files:

      You do not release the FDT to the school, you need to release the DDM for the file and you use SYSOBJH to unload that. You have to specify SYSTEM as the Library name (and specify a range (ex: W*1415*) for the . (They are STILL considered “Natural library objects”).
    • SYSOBJH (Object load)
      • To load Natural objects (programs, subprograms, maps, copycode, etc.) from a library, there’s a special version of Natural “D – WolffPack DBA function” (as opposed to W – WolffPack Development) which accesses special work files. After getting into Natural via “D”, go to the Direct Command line and issue the command “SYSOBJH”.

       

      Notes: The file must be formatted appropriately (see notes below).
      When you are finished with the SYSOBJH, make sure you select No on the ‘Do you want to continue the unload function?’ Screen and press Enter.

      The dataset should be in your home directory (ex:/home/hartwigd) and defaults to ($)cmwkf01.dat I just tend to use that. (Note, I’ve only done SOURCE code updates to FATEMP2, I’d recommend using a non WPDEV library.
      To make a non-line number source code into a SYSOBJH file:

      • 1. Source code:
           • Add ‘*S**’ to the beginning of EVERY line (Comments (*) would then start in column 5).
        2. Header:

           *H**ANAT6205201206130806442LINUX                            4CAUC     03.0
           *C**                                FATEMP2 FPPLS13N                        N S   N
           *D01NAT6205N FATEMP2 FPPLS13N                        HARTWIGDHARTWIGD        S
           *D02            2012061110300002012061110300000000042532
           *D03LINUX
           *D04                 ISO_8859-1:1987
           

        3. Change all occurrences of:
           • FPPLS13N: to your source module name
           • FATEMP2: to your UPLOAD library name
           • HARTWIGD: (will get changed when you stow it, so you can ignore it for now…)
        4. Footer:
           • Add ‘*E’ to the beginning of the last line of the source code.
    • Linux/Unix commands – At the command prompt: (ex: hartwigd@PNSANDBOX:~>)The Linux box we have access to uses bash shell, here’s a link to various commands: http://ss64.com/bash/
      • Directory – ‘ls‘
      • Directory (with details) – ‘ls -lh‘
      • Change working directory (up one) – ‘cd ..‘ (cd = change directory)
      • Change working directory (down to bin subdirectory) – ‘cd bin‘ (prompt should reflect new directory)
      • Search for text in file (Search for Mom in file gift-ideas.txt) – ‘grep Mom gift-ideas.txt‘
      • List files (with search) (Search for all .txt files) – ‘ls | grep .txt‘
      • List files (and output list to file “file-listing.txt”) – ‘ls > file-listing.txt‘
      • Display file contents (ex: filename.txt) – ‘cat filename.txt‘
      • copy file to another (ex: oldfile (may have extensions)) – ‘cp oldfile newfile‘

• • Graphical access
    • Note: The programs listed below with a double asterisk (**) have been installed in the “loaded” VM. If you are using the “loaded” VM, you do NOT have to re-install these programs.

     

    • Using WinSCP** (a graphical FTP/Explorer like interface) we can edit and navigate graphically (remember, the IP address is: 172.31.254.124)
      • Editing: You can assign an external editor (I use Notepad++) instead of using the default notepad-like editor.NOTE: This gets us OUT of needing to learn/use VI!
        • Preferences: Add editor, move it “up” the list of editors (uses the first one)
        • Copy/Duplicate: Right click and select copy/duplicate
    • Another alternative to editing remotely is to use an editor that has SCP (Secure Copy Protocol) built right in. Komodo Edit** is such a Windows (freeware) editor with SCP access.Note: This allows for navigation of the remote Linux server WITHOUT need for WinSCP (but you’ll need to add a plugin: RemoteDriveTree)

• • Directory Notes/Job Submission:
    • Job submission is done using WinSCP out of a shared library: “/data/wolffpack/scripts”.
      • We’ve used the naming convention suffixed with a “J” (ex: WFADDLDJ) for jobs. Dictionary import and export jobs are the exception and just have a “B” on the end.
      • Navigate there in WinSCP, edit the job and modify the parameters as appropriate.
    • To execute, click the “HOM” button, which is the Open Terminal button, in the WinSCP window. A console window will pop up and you will then enter the name of the job you want to execute (ex: “WFADDLDJ” ) in the “enter Command” box and click execute. There is no message to tell you that the job completed but you will not be able to close the console window until it is completed. When you can, close the window.
    • Job output that exists as print files is found in the /scripts library (where the jobs are located). The jobname is appended to the stepname along with the print file type (ex: wfaddldj.step1.cmprt01). The job output that exists as a workfile is found in the /work library.
      • A detailed breakdown of what jobs look/function like was supplied to us by Sophia, view it here.

• Job List:
  Jobs created/tested in mig/wolffpack/scripts

  Job / scriptDescription

  wfaddimj	Add Import
  wfaddldj	Add Load
  wfappclj	Application (Requirements) Calc
  wfawardj	Award Process
  wfbgtclj	Budget Calc
  wfecoexj	EDE Corrections Export
  wfdsbclj	Disbursement (Requirements) Calc
  wfnanclj	Need Analysis Calc
  wfvcnclj	Verification Calc
  wwdiclsj	Dictionary Listing
  wcdicexb	Dictionary Export
  wcdicimb	Dictionary Import

chmod u+x wfcbwexj (To allow execute permissions on WFCBWEXJ)

chmod u+w danwork1.txt (To allow execute permissions on DANTEXT1.TXT)