Filter
Top Products
25
However, if a small amount of real memory is used (< 100 MB), due
to a lack of BCAM memory this can lead to problems occurring
during connection setup or to low transaction rates. This behav-
ior can be improved by increasing the PAGMEM and RESMEM values.
Memory monitoring can be activated with the BCAM /BCMON command
(RECORD=(RES-MEMORY,PAG-MEMORY)) and this allows detection of
whether the current values reach the limits.
Any adjustments to the memory values should only be made in
agreement with the responsible first level support.
3.4.2 SPARC64 command set and code variants
SPARC64 processors run in the SX servers and they can only execute
SPARC64 code directly (native). The command set, command format and
the program context differ fundamentally from the /390 environment.
However, it is also possible to run /390 code object-compatibly
due to a special CISC firmware layer. The just-in-time /390 code
translator (JIT) optimizes this emulation by translating the /390
code temporarily into SPARC64 code and buffering it internally.
Three code variants are executable on the SX servers under the
OSD/XC V2.2A operating system in TU:
- /390 code: series of commands in /390 mode.
- SPARC64 code: series of commands in SPARC64 mode.
- Mixed binary code: series of commands containing /390
and SPARC64 code as well as provisions for changing
between /390 and SPARC64 mode.
System exits and privileged customer programs
All privileged OSD/XC routines must exist as SPARC64 code.
This includes:
- System exit routines
- Programs with TPR parts that are activated via SVC79.
(Note: SVC79 has been replaced by the CAPRI subsystem).
If you use privileged programs, the program source code must be
cleaned up and then recompiled in all cases.
Fujitsu Siemens Computers offers you advice and support for this.
Please contact your service delegate. The tools and documentation
required for conversion will be provided to you under special re-
lease.
Non-privileged customer programs
Non-privileged customer programs can only be generated in /390
code.
You need the ASSEMBH assembler as of V1.2 for new compilations with
the OSD/XC V2.2A macro libraries.
Debugging and diagnosis
The products DAMP and AID are available for debugging and diagnos-
ing non-privileged customer programs.