PBS has changed the contents of $PBS_NODEFILE, now lists FQDN

Description

Hola,
In my testing, I\'ve discovered that the contents of the nodefile created for a job by PBS have changed. If my job runs on node xyz under old PBS version the nodefile looks like:
xyz
If I run under present PBS version it looks like:
xyz.p4.localhost
I believe the difference is that the present version pbs_mom, in job_nodes(), checks the value of enable_exechost2 and decides how to call create_mommap_entry(). enable_exechost2 is a flag that says whether pbs_mom is connected to present version server. Why should the value of enable_exechost2 change the nodefile? I didn\'t see anything in the release notes, and the present version User\'s guide says that the nodefile should contain entries according to the value of resources_available.host for allocated vnodes. Here\'s what pbsnodes says about xyz:
pbsnodes xyz
xyz
Port = 15002
ntype = PBS
state = free
pcpus = 16
resources_available.aoe = sles11,sles11h,sles11j,sles11k,sles11m,sles11o
resources_available.arch = linux
resources_available.host = xyz
resources_available.mem = 24635008kb
resources_available.model = neh
resources_available.ncpus = 16
resources_available.reboot = free
resources_available.vnode = xyz
resources_assigned.accelerator_memory = 0kb
resources_assigned.mem = 0kb
resources_assigned.naccelerators = 0
resources_assigned.ncpus = 0
resources_assigned.netwins = 0
resources_assigned.vmem = 0kb
resv_enable = True
sharing = default_excl
provision_enable = True
current_aoe = sles11h
In my scenario we don\'t have a vnodemap.
-Customer
Original title was: enable_exechost2 alters the contents of $PBS_NODEFILE

Acceptance Criteria

None

Status

Assignee

Unassigned

Reporter

Former user

Severity

None

OS

None

Start Date

None

Pull Request URL

None

Components

Priority

High
Configure