| ! I replaced our copies of FUSELIB.EXE and FUSEOBJ.OLB
! and now the subroutines seem to work, with the exception
! of subroutines which call other subroutines ( Im still
! trying to figure that one out ). I thought I may as well
! save somebody some typing so here is the MTHNAM program
! in VAX BASIC ( see User Subroutine Manual).
!
!
!
!
1000 SUB MTHNAM BY REF (DOUBLE MTH, STRING MONTH = 12)
2000 ON INTEGER (MTH) GOTO 2001,2002,2003,2004,2005,2006, &
2007,2008,2009,2010,2011,2012 &
OTHERWISE 2013
2001 MONTH = "JANUARY "
EXIT SUB
2002 MONTH = "FEBRUARY "
EXIT SUB
2003 MONTH = "MARCH "
EXIT SUB
2004 MONTH = "APRIL "
EXIT SUB
2005 MONTH = "MAY "
EXIT SUB
2006 MONTH = "JUNE "
EXIT SUB
2007 MONTH = "JULY "
EXIT SUB
2008 MONTH = "AUGUST "
EXIT SUB
2009 MONTH = "SEPTEMBER "
EXIT SUB
2010 MONTH = "OCTOBER "
EXIT SUB
2011 MONTH = "NOVEMBER "
EXIT SUB
2012 MONTH = "DECEMBER "
EXIT SUB
2013 MONTH = "**ERROR** "
EXIT SUB
3000 END SUB
|
| My group uses FUSELIB extensively: all our menus are subroutines
in FUSELIB that are called within dialogue manager. In this manner
we invoke COBOL/FMS menus which are sharable images of FOCUS - instead
of spawning subprocesses -and/or- resorting to HLI.
While the majority of our routines are application specific, we
do have a couple of subroutines for general usage - such as a fiscal
date conversion routine - which is nothing more than an old COBOL
routine tossed into FUSELIB.
If you contact me directly, I'll point to you some programmers who
work with FUSELIB every day.
-rpr-
223-1334
|