[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference humane::scheduler

Title:SCHEDULER
Notice:Welcome to the Scheduler Conference on node HUMANEril
Moderator:RUMOR::FALEK
Created:Sat Mar 20 1993
Last Modified:Tue Jun 03 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1240
Total number of notes:5017

1136.0. "ALPHA OpenVMS and callable interface" by 26115::CONNOLLY () Thu Jul 25 1996 13:31


	ALPHA OpenVMS V6.2
	POLYCENTER Scheduler V2.1

	The installation of Scheduler asked nothing about
	installing the callable interface unlike the VMS
	installation kit.

	I got my hands on the alpha openvms CDs and found
	the C header files and axp_*.olb for scheduler.

	I compiled and linked and I got undefined symbols
	yet when yet the program checked if the job was
	in the scheduler que and then created the job.

	How do I resolve the undefined symbols?

	the attached is the results of the cc and link:


$cc/noopt/standard=vaxc/define=__VMS_CURSES/debug/show=all/list/warnings/object=CONFIG.obj CONFIG.c
$!
$link/debug/exe=CONFIG CONFIG.obj,-
        nsched$:axp_nsched_subs/lib, -
        nsched$:axp_nsched_remote/lib
%LINK-W-NUDFSYMS, 4 undefined symbols:
%LINK-I-UDFSYM,         EXE$GL_SYSTICK
%LINK-I-UDFSYM,         PFN$GL_PHYPGCNT
%LINK-I-UDFSYM,         SCH$GL_FREECNT
%LINK-I-UDFSYM,         SMP$GL_CPU_DATA
%LINK-I-UDFSYM,         SYNC_CREATE (Weak Reference)
%LINK-I-UDFSYM,         SYS$CHANGE_ACL (Weak Reference)
%LINK-I-UDFSYM,         VSS$BIND (Weak Reference)
%LINK-I-UDFSYM,         VSS$SHOW_PARAMS (Weak Reference)
%LINK-I-UDFSYM,         WRITE_SCHEDULER_MBX (Weak Reference)
%LINK-W-USEUNDEF, undefined symbol PFN$GL_PHYPGCNT referenced
        in psect $LINK$ offset %X00000160
        in module SCHED_RTL file USER01:[NSCHED]AXP_NSCHED_SUBS.OLB;1
%LINK-W-USEUNDEF, undefined symbol SCH$GL_FREECNT referenced
        in psect $LINK$ offset %X00000180
        in module SCHED_RTL file USER01:[NSCHED]AXP_NSCHED_SUBS.OLB;1
%LINK-W-USEUNDEF, undefined symbol SMP$GL_CPU_DATA referenced
        in psect $LINK$ offset %X000001A0
        in module SCHED_RTL file USER01:[NSCHED]AXP_NSCHED_SUBS.OLB;1
%LINK-W-USEUNDEF, undefined symbol EXE$GL_SYSTICK referenced
        in psect $LINK$ offset %X000001C8
        in module SCHED_RTL file USER01:[NSCHED]AXP_NSCHED_SUBS.OLB;1
$
	
T.RTitleUserPersonal
Name
DateLines
1136.1sloppy kittingRUMOR::FALEKex-TU58 KingFri Jul 26 1996 11:5821
    The 4 undefined symbols all have to do with calculating the service ratings
    used for load balancing, and are only used by the scheduler (NSCHED
    process) never anything outside of NSCHED (like the user interface or
    anything you might write to affect the scheduler) so they shouldn't
    cause any damage.
    
    I suspect that the developers included a routine in the AXP version of
    NSCHED_SUBS that shouldn't be there - on the VAX version, those symbols
    are referenced in module RATINGS_AST (or something with a similar name)
    and resolved in sys$library:sys.stb (which doesn't exist on ALPHA VMS).
    Since your code will never go anywehere near these, you could you make
    the warnings go away by creating a linker options file that defines the
    4 symbols as zero.  Or you could find the module containing the
    refernces and remove it from the .OLB file, then relink.
    I'd say this is a bug with the kitting - If you can figure out how to
    report it, it should be reported (to Computer Associates).
    
    The weak referneces you can also ignore, since they are routines that
    are declared, but not used. They are for remove support using the old 
    VAX RPC communication mechanism, which is not used on Alpha. There should
    have been conditional compilation around those declarations.
1136.2Use /SYSEXEKETJE::MICHIELShttp://brsadv.bro.dec.com/Wed Jul 31 1996 02:5811
    I recently run in the same problem, and solved it as follows:
    
    $ LINK CPT$CREATE_SCHEDULER_JOB,NSCHED$:AXP_NSCHED_SUBS/LIB/SYSEXE
    
    
    The /SYSEXE solved the problem, but I believe you might need a relink
    of your application after an upgrade of OpenVMS.
    
    Hope this helps,
    
    Johan