J06.14 Release Version Update Compendium

3 Application Development Products
Two TSMSGIP Processes per CPU
As of RVU J06.14, two instances of the TSMSGIP process exist on each CPU on 4-IPU systems,
such as a NonStop BladeSystem NB54000c. By default, both instances are assigned to IPU 0.
For certain workloads with high levels of inter-CPU Message System traffic, reassigning one of the
instances to another IPU, using the IPUAFFINITY_SET_procedure can be beneficial.
For more information on the TSMSGIP process and how to assign instances of TSMSGIP to IPUs,
see the Guardian Programmer’s Guide.
Migration Considerations
This feature requires the J06.14 or later RVU.
Fallback Considerations
None.
Passwords in the Clear
The TNS/E C/C++ Compiler, TNS/E COBOL Compiler, and the TNS/E Code Coverage tool
encrypt user credentials (secure encrypted mode) when they communicate from a Windows client
to an NSK server. This can reduce overall compilation performance. The user can control the mode
by using either a command-line option or an environment variable.
Migration Considerations
To connect using a secure mode, J06.14 must be installed on the NSK server and SSH must be
running on the NSK system. To connect securely to NSK servers running RVUs prior to J06.14,
T0246H01^AAS and T0801H01 are required.
Fallback Considerations
None.
NonStop Binary Semaphores (BINSEM)
The J06.14, RVU adds instrumentation to the NonStop binary semaphore (BINSEM) routines used
to measure possible application bottlenecks. New features include:
• SEMSTAT utility program
Provides usage statistics for a particular process
• binSemStats_t data structure
• BINSEM-related Guardian procedures:
BINSEM_GETSTATS_
Provides BINSEM statistics for a specified process
BINSEM_STAT_VERSION_
For a kbinsem.h version, provides the length (in bytes) of the binSemStats_t structure
in the implementation of BINSEM_GETSTATS_
The binSemStats_t structure and the BINSEM_STAT_VERSION_ and BINSEM_GETSTATS_
procedures are version sensitive. For best results, applications that call BINSEM_GETSTATS_ should
first call BINSEM_STAT_VERSION_ to ensure that the binSemStats_t structure used in the
program is compatible with the system where the application is run.
12 Application Development Products