z/OS


IBM Ported Tools for z/OS: Xvfb User's

Guide

SA23-2216-00
z/OS


IBM Ported Tools for z/OS: Xvfb User's

Guide

SA23-2216-00
 Note
Before using this information and the product it supports, be sure to read the general information under “Notices” on page
19.

This edition applies to version 1 release 2, modification 0 of IBM Ported Tools for z/OS (5655-M23) and to all
subsequent releases and modifications until otherwise indicated in new editions.
© Copyright IBM Corporation 2010.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this document . . . . . . . . . v Signals . . . . . . . . . . . . . . . 4
Who should use this document? . . . . . . . . v Examples . . . . . . . . . . . . . . 4
Where to find more information . . . . . . . . v Authors . . . . . . . . . . . . . . . 4
Softcopy publications . . . . . . . . . . v
IBM Ported Tools for z/OS home page . . . . v Chapter 2. Xvfb messages . . . . . . . 5

How to send your comments to IBM . . vii Notices . . . . . . . . . . . . . . 19

If you have a technical problem . . . . . . . vii Programming Interface Information . . . . . . 19
Trademarks . . . . . . . . . . . . . . 19
Summary of changes . . . . . . . . . ix
Accessibility . . . . . . . . . . . . 21
Chapter 1. Xvfb — Virtual framebuffer X Using assistive technologies . . . . . . . . . 21
Server for X Version 11 . . . . . . . . 1 Keyboard navigation of the user interface . . . . 21
Synopsis . . . . . . . . . . . . . . . . 1 z/OS information . . . . . . . . . . . . 21
Description . . . . . . . . . . . . . . . 1
Options . . . . . . . . . . . . . . . . 1 Index . . . . . . . . . . . . . . . 23
Xserver options . . . . . . . . . . . . 1

© Copyright IBM Corp. 2010 iii

iv z/OS V1.1.0 IBM Ported Tools for z/OS: Xvfb
About this document
This document presents the information you need to set up and use the Xvfb
program product.

In IBM Ported Tools for z/OS V1.2, the Xvfb code is delivered as a separate FMID,
HVFB111 and is available only with the IBM Ported Tools for z/OS 245 FMID
HOS1120. The Xvfb for z/OS code in FMID HVFB111 is the same code that was
available as PTFs UA21819 and UA32671 with IBM Ported Tools for z/OS V1.1.
The Xvfb for z/OS code is delivered as a separate FMID in order to allow IBM to
provide more efficient support.

Who should use this document?

This document is for the system programmers who run a z/OS system with z/OS
UNIX System Services (z/OS UNIX), and for their users who use the Xvfb portion
of IBM Ported Tools for z/OS. On other open systems, some system programmer
tasks might be done by an administrator.

This document assumes that the readers are familiar with z/OS systems and with
the information for z/OS systems and the accompanying products.

Where to find more information

Where necessary, this document references information in other documents about
the elements and features of z/OS®. For complete titles and order numbers for all
z/OS documents, see z/OS Information Roadmap.

Softcopy publications
Softcopy z/OS publications are available for web-browsing and PDF versions of
the z/OS publications for viewing or printing using Adobe® Acrobat Reader. Visit
the z/OS library at http://www.ibm.com/systems/z/os/zos/bkserv/.

IBM Ported Tools for z/OS home page

The IBM Ported Tools for z/OS home page is located at www.ibm.com/servers/
eserver/zseries/zos/unix/port_tools.html. It contains a brief description of the
IBM Ported Tools for z/OS products, information on how to order them, and
supporting documentation.

To order IBM Ported Tools for z/OS: Xvfb, go to the IBM® ShopzSeries Web site at
www14.software.ibm.com/webapp/ShopzSeries/ShopzSeries.jsp. Customers can
report problems found with this product through their normal support structure

© Copyright IBM Corp. 2010 v

vi z/OS V1.1.0 IBM Ported Tools for z/OS: Xvfb
How to send your comments to IBM
We appreciate your input on this publication. Feel free to comment on the clarity,
accuracy, and completeness of the information or give us any other feedback that
you might have.

Use one of the following methods to send us your comments:

1. Send an e-mail to [email protected]
2. Visit the Contact z/OS Web page at http://www.ibm.com/servers/eserver/
zseries/zos/webqs.html
3. Mail the comments to the following address:
IBM Corporation
Attention: MHVRCFS Reader Comments
Department H6MA, Mail Station P181
2455 South Road
Poughkeepsie, NY 12601-5400
U.S.A.
4. Fax the comments to us as follows:
From the United States and Canada: 1+845+432-9405
From all other countries: Your international access code +1+845+432-9405

Include the following information:

v Your name and address
v Your e-mail address
v Your telephone or fax number
v The publication title and order number:
IBM Ported Tools for z/OS: Xvfb User's Guide
SA23-2216-00
v The topic and page number related to your comment
v The text of your comment.
When you send comments to IBM, you grant IBM a nonexclusive right to use or
distribute your comments in any way it believes appropriate without incurring any
obligation to you.

IBM or any other organizations will only use the personal information that you
supply to contact you about the issues that you submit.

If you have a technical problem

Do not use the feedback methods listed above. Instead, do one of the following:
v Contact your IBM service representative
v Call IBM technical support
v Visit the IBM zSeries support Web page at http://www.ibm.com/servers/
eserver/support/zseries/

© Copyright IBM Corp. 2010 vii

viii z/OS V1.1.0 IBM Ported Tools for z/OS: Xvfb
Summary of changes
Summary of changes
for SA23-2216-00
IBM Ported Tools for z/OS: Xvfb

The document contains information previously presented in IBM Ported Tools for
z/OS User's Guide, SA22-7985-06. The OpenSSH section is now in IBM Ported Tools
for z/OS: OpenSSH User's Guide, SA23-2246-00.

© Copyright IBM Corp. 2010 ix

x z/OS V1.1.0 IBM Ported Tools for z/OS: Xvfb
Chapter 1. Xvfb — Virtual framebuffer X Server for X Version
11
Synopsis
Xvfb [ option ] . . .

Description
Xvfb is an X server that can run on machines with no display hardware and no
physical input devices. It emulates a dumb framebuffer using virtual memory.

The primary use of this server was intended to be server testing. The mfb or cfb
code for any depth can be exercised with this server without the need for real
hardware that supports the desired depths. The X community has found many
other novel uses for Xvfb, including testing clients against unusual depths and
screen configurations, doing batch processing with Xvfb as a background rendering
engine, load testing, as an aid to porting the X server to a new platform, and
providing an unobtrusive way to run applications that don't really need an X
server but insist on having one anyway.

Options
In addition to the normal server options described in the Xserver Options section,
Xvfb accepts the following command line switches:
-screen screennum WxHxD
This option creates screen screennum and sets its width, height, and depth
to W, H, and D respectively. By default, only screen 0 exists and has the
dimensions 1280x1024x8.
-pixdepths list-of-depths
This option specifies a list of pixmap depths that the server should support
in addition to the depths implied by the supported screens. list-of-depths is
a space-separated list of integers that can have values from 1 to 32.
-linebias n
This option specifies how to adjust the pixelization of thin lines. The value
n is a bitmask of octants in which to prefer an axial step when the
Bresenham error term is exactly zero. This option is probably only useful
to server developers to experiment with the range of line pixelization
possible with the cfb and mfb code.
-blackpixel pixel-value, -whitepixel pixel-value
These options specify the black and white pixel values the server should
use.

Xserver options
:displaynumber
The X server runs as the given displaynumber, which by default is 0. If
multiple X servers are to run simultaneously on a host, each must have a
unique display number.

© Copyright IBM Corp. 2010 1

Xvfb

-a number
Sets pointer acceleration (that is, the ratio of how much is reported to how
much the user actually moved the pointer).
-ac Disables host-based access control mechanisms. Enables access by any host,
and permits any host to modify the access control list. Use with extreme
caution. This option exists primarily for running test suites remotely.
-audit level
Sets the audit trail level. The default level is 1, meaning only connection
rejections are reported. Level 2 additionally reports all successful
connections and disconnects. Level 0 turns off the audit trail. Audit lines
are sent as standard error output.
-auth authorization-file
Specifies a file which contains a collection of authorization records used to
authenticate access. See also the xdm and Xsecurity manual pages.
bc Disables certain kinds of error checking, for bug compatibility with
previous releases (such as working work around bugs in R2 and R3 xterms
and toolkits). Deprecated.
-bs Disables backing store support on all screens.
-br Sets the default root window to solid black instead of the standard root
weave pattern.
-c Turns off key-click.
c volume
Sets key-click volume (allowable range: 0-100).
-cc class
Sets the visual class for the root window of color screens. The class
numbers are as specified in the X protocol.
-co filename
Sets name of RGB color database.
-core Causes the server to generate a core dump on fatal errors.
-dpi resolution
Sets the resolution of the screen, in dots per inch. To be used when the
server cannot determine the screen size from the hardware.
-deferglyphs whichfonts
Specifies the types of fonts for which the server should attempt to use
deferred glyph loading. whichfonts can be one of the following:
v All (all fonts)
v None (no fonts)
v 16 (16 bit fonts only)
-f volume
Sets feep (bell) volume (allowable range: 0-100).
-fc cursorFont
Sets the default cursor font.
-fn font
Sets the default font.
-fp fontPath
Sets the search path for fonts. This path is a comma separated list of
directories which the X server searches for font databases.

2 z/OS V1.1.0 IBM Ported Tools for z/OS: Xvfb

 Xvfb

-help Prints a usage message.

-I Causes all remaining command line arguments to be ignored.
-nolisten trans-type
Disables a transport type. For example, TCP/IP connections can be
disabled with -nolisten tcp.
-noreset
Prevents a server reset when the last client connection is closed. This
overrides a previous -terminate command line option.
-p minutes
Sets screen-saver pattern cycle time in minutes.
-pn Permits the server to continue running if it fails to establish all of its
well-known sockets (connection points for clients), but establishes at least
one.
-r Turns off auto-repeat.
r Turns on auto-repeat.
-s minutes
Sets screen-saver timeout time in minutes.
-su Disables save under support on all screens.
-t number
Sets pointer acceleration threshold in pixels (that is, after how many pixels
pointer acceleration should take effect).
-terminate
Causes the server to terminate at server reset, instead of continuing to run.
This overrides a previous -noreset command line option.
-to seconds
Sets default connection timeout in seconds.
-tst Disables all testing extensions (for example, XTEST, XTrap,
XTestExtension1, RECORD).
ttyxx Ignored, for servers started the ancient way (from init).
v Sets video-off screen-saver preference.
-v Sets video-on screen-saver preference.
-wm Forces the default backing-store of all windows to be WhenMapped. This
is a backdoor way of getting backing-store to apply to all windows.
Although all mapped windows will have backing store, the backing store
attribute value reported by the server for a window will be the last value
established by a client. If it has never been set by a client, the server will
report the default value, NotUseful. This behavior is required by the X
protocol, which allows the server to exceed the client's backing store
expectations but does not provide a way to tell the client that it is doing
so.
-x extension
Loads the specified extension at init. This is a no-op for most
implementations.
[+-]xinerama
Enables(+) or disables(-) the XINERAMA extension. The default state is
disabled.

Chapter 1. Xvfb — Virtual framebuffer X Server for X Version 11 3

Xvfb

Signals
The X server attaches special meaning to the following signals:
SIGHUP
This signal causes the server to close all existing connections, free all
resources, and restore all defaults. It is sent by the display manager
whenever the main user's main application (usually an xterm or window
manager) exits to force the server to clean up and prepare for the next
user.
SIGTERM
This signal causes the server to exit cleanly.
SIGUSR1
This signal is used quite differently from either of the above. When the
server starts, it checks to see if it has inherited SIGUSR1 as SIG_IGN
instead of the usual SIG_DFL. In this case, the server sends a SIGUSR1 to
its parent process after it has set up the various connection schemes. Xdm
uses this feature to recognize when connecting to the server is possible.

Examples
1. Xvfb :1 -screen 0 1600x1200x32
The server will listen for connections as server number 1, and screen 0 will be
depth 32 1600x1200.
2. Xvfb :1 -screen 1 1600x1200x16
The server will listen for connections as server number 1, will have the default
screen configuration (one screen, 1280x1024x8), and screen 1 will be depth 16
1600x1200.
3. Xvfb -pixdepths 3 27 -fbdir /usr/tmp
The server will listen for connections as server number 0, will have the default
screen configuration (one screen, 1280x1024x8), will also support pixmap
depths of 3 and 27, and will use memory mapped files in /usr/tmp for the
framebuffer.
4. xwud -in /usr/tmp/Xvfb_screen0
Displays screen 0 of the server started by the preceding example.

Authors
David P. Wiggins, The Open Group, Inc.

4 z/OS V1.1.0 IBM Ported Tools for z/OS: Xvfb

Chapter 2. Xvfb messages
contains an appropriate boolean value.
XVFB0001 number spans
Explanation: Informational printing of the number
XVFB0010 expected a numeric value on line number
spanned.
Explanation: While parsing the xkb configuration file,
User response: None.
the program failed to find an expected numeric value
at the specified line.
XVFB0004 allocation failed
User response: Verify that the line in question
Explanation: While parsing the xkb configuration file, contains an appropriate numeric value.
the program failed to allocate memory.
User response: Verify that the system has enough XVFB0011 expected a string on line number
resources available for use.
Explanation: While parsing the xkb configuration file,
the program failed to find a string at the specified line.
XVFB0005 unterminated string on line number
User response: Verify that an appropriate string exists
Explanation: While parsing the xkb configuration file, at the line in question.
the program encountered a non-terminated string at the
specified line.
XVFB0012 expected a modifier name on line
User response: Verify that the line in question has a number
correct termination character.
Explanation: While parsing the xkb configuration file,
the program failed to find a modifier name at the
XVFB0006 expected identifier on line number specified line.
Explanation: While parsing the xkb configuration file, User response: Verify that a modifier name exists at
the program failed to find an expected identifier on the the line in question.
specified line.
User response: Verify that the line in question XVFB0013 expected a control name on line number
contains the correct identifier.
Explanation: While parsing the xkb configuration file,
the program failed to find an expected control name on
XVFB0007 expected '=' on line number the specified line.
Explanation: While parsing the xkb configuration file, User response: Verify that an appropriate control
the program failed to find an expected '=' character on name exists at the line in question.
the specified line.
User response: Verify that the line in question XVFB0014 expected an AccessX option on line
contains a '='. number
Explanation: While parsing the xkb configuration file,
XVFB0008 expected ';' or newline on line number the program failed to find an expected AccessX option
on the specified line.
Explanation: While parsing the xkb configuration file,
the program failed to find an expected ';' or newline on User response: Verify that an AccessX option exists at
the specified line. the line in question.
User response: Verify that the line in question
contains a ';' or newline. XVFB0015 expected '+' or '-' on line number
Explanation: While parsing the xkb configuration file,
XVFB0009 expected a boolean value on line number the program failed to find an expected '+' or '-' at the
specified line.
Explanation: While parsing the xkb configuration file,
the program failed to find a boolean value at the User response: Verify that the line in question
specified line. contains either a '+' or '-'
User response: Verify that the line in question

© Copyright IBM Corp. 2010 5

XVFB0016 expected wrap, clamp or group number XVFB0025 ProgramName: unable to open display
on line number XDisplayName
Explanation: While parsing the xkb configuration file, Explanation: The program is unable to open the
the program failed to find an expected wrap, clamp or specified display.
group number on the specified line.
User response: Verify that any necessary network
User response: Verify that the line in question connections are available and the display in question is
contains an appropriate wrap, clamp or group number. a valid display.

XVFB0017 unknown error on line number XVFB0026 access control enabled, only authorized
clients can connect
Explanation: While parsing the xkb configuration file,
the program encountered an unknown error at the Explanation: Informational message. User has
specified line. activated the access control features.
User response: Examine the xkb configuration file for User response: None.
any anomalies or stray characters. Verify that all
options are correct.
XVFB0027 access control disabled, clients can
connect from any host
XVFB0019 XTestEXTENSION_NAME: invalid
Explanation: Informational message. User has
key/button state keystate.
deactivated the access control features.
Explanation: The current key state is not in either a
User response: None.
pressed or released state.
User response: Verify that the keyboard is not faulty,
XVFB0028 unknown address in family list[i].family
as a key should only be able to reside in one of the two
states. Explanation: When looking up the hostname, an
unexpected value was returned.
XVFB0021 Default symbols not implemented yet! User response: Verify that you are attempting to use a
valid hostname, such as localhost.
Explanation: No keycode was specified in the
configuration and there are no default symbols
available. XVFB0029 (no nameserver response within
NAMESERVER_TIMEOUT seconds)
User response: Provide the program with a specific
keycode map in the configuration. Explanation: The nameserver failed to respond within
the set timeout window.
XVFB0022 Default types not implemented yet! User response: Verify that the connection is free of
bandwidth problems or increase the timeout window.
Explanation: No type was specified in the
configuration and there are no default types available.
XVFB0030 ProgramName: bad hostname arg
User response: Provide the program with a specific
type in the configuration. Explanation: A bad hostname has been provided to
the program.
XVFB0023 Default interps not implemented yet! User response: Verify that you are attempting to use a
valid hostname.
Explanation: No interups were specified in the
configuration and there are no default interups
available XVFB0031 ProgramName: malloc bombed in
change_host
User response: Provide the program with a specific
interup in the configuration. Explanation: The given program name has failed
when attempting to call malloc.
XVFB0024 No file User response: Verify that the system has enough
available resources.
Explanation: No file name was given to test
authorization.
User response: Ensure that the complete list of
paramaters has been passed into the program.

6 z/OS V1.1.0 IBM Ported Tools for z/OS: Xvfb

 change_host function cannot parse the supplied
XVFB0032 ProgramName: not compiled for TCP/IP
Kerberos name, this error will occur. Verify that the
Explanation: The given program has not been data passed into the program is correct and formatted
compiled with TCP/IP support. properly.
User response: You must recompile the binaries,
adding in support for TCP/IP. XVFB0039 non-network local connections
add_msg/remove_msg
XVFB0033 ProgramName: not compiled for DECnet Explanation: You are adding or removing a
non-network local connection.
Explanation: The given program has not been
compiled with DECnet support. User response: None.
User response: You must recompile the binaries,
adding in support for DECnet. XVFB0040 no such user name
Explanation: No such user name exists.
XVFB0034 ProgramName: not compiled for Secure
User response: If SECURE_RPC is defined and the
RPC
given user name cannot be found, this error will occur.
Explanation: The given program has not been Verify that the given user name is valid and exists.
compiled with Secure RPC support.
User response: You must recompile the binaries, XVFB0041 failed to get netname for name
adding in support for Secure RPC.
Explanation: Failed to get netname for the given
name.
XVFB0035 ProgramName: not compiled for Kerberos
User response: If SECURE_RPC is defined and the
5
netname for the given name cannot be found, this error
Explanation: The given program has not been will occur. Verify that the given user name is valid and
compiled with Kerberos 5 support. the netname exists.
User response: You must recompile the binaries,
adding in support for Kerberos 5. XVFB0042 ProgramName: must be on local machine
to add or remove hosts.
XVFB0036 ProgramName: unknown address family Explanation: The given program must be on the local
lname machine to add or remove hosts.
Explanation: The given program encountered an User response: You are trying to add or remove hosts
unknown address family. from a remote machine. For security reasons, you must
be on the local machine to perform such an action.
User response: This error occurs when trying to edit
Ensure you are on the local machine and try again.
the list of hosts that may connect to the server. Verify
that the information you are trying to add or edit is in
the correct format. XVFB0043 ProgramName: must be on local machine
to enable or disable access control.
XVFB0037 ProgramName: unable to get node name Explanation: The given program must be on the local
for name:: machine to enable or disable access control.
Explanation: The given program is unable to retrieve User response: You are trying to enable or disable
the node name access control from a remote machine. For security
reasons, you muct be on the local machine to perform
User response: When compiled with DNETCONN, if
such an action. Ensure that you are on the local
the change_host function cannot parse the given host
machine and try again.
name to find the correct node, this error will occur.
Verify that the host name is correct and in the correct
format. XVFB0044 bad display name dpy in cmd command
Explanation: A bad display name was entered in the
XVFB0038 ProgramName: cannot parse Kerberos given command.
name: error_message(retval))
User response: Verify that the given display name is
Explanation: The given program is unable to parse the valid and properly formatted.
shown Kerberos name
User response: When compiled with K5AUTH, if the

Chapter 2. Xvfb messages 7

 User response: Verify that there is sufficient system
XVFB0045 bad cmd command line
resources available for use.
Explanation: You have entered a bad command from
the command line.
XVFB0052 Attempting to break locks on authority
User response: The most probable cause of this error file authfilename
is an incorrect argument list being input from the
Explanation: The program is trying to break the locks
command line. Verify that the syntax for the command
on the authority file.
in question.
User response: None.
XVFB0046 cmd: stdin already in use
XVFB0053 ProgramName: errormsg in locking
Explanation: When trying to open a file, standard in
authority file authority filename
was found to be in use.
Explanation: An error occurred when trying to lock
User response: Another process has set the
the given file name.
okay_to_use_stdin flag to false. Wait for this process to
finish or manually kill the process. User response: There are 3 possible error: unknown,
timeout, and error. For timeout errors, the problem is
typically related to network latency issues or a lack of
XVFB0047 cmd: unable to open file filename
available resources on the machine. Verify that the
Explanation: While attempting to open the file name environment is in working order. An "error" error is
in question, fopen failed. indicative of permission or file locked issues. Verify
that authority file has the correct permission settings.
User response: Verify that the file exists with the
Unknown errors encompass all other problems.
correct permissions. If attempting to create the file,
ensure that you have permission to do so. Furthermore,
verify that no other processes have the file in question XVFB0054 ProgramName: authority filename not
open or locked. writable, changes will be ignored"
Explanation: After establishing a lock on the authority
XVFB0048 ProgramName: unable to alloc entry file, the program could not write to the file.
reading auth file
User response: After the program has successfully
Explanation: The call to malloc failed when trying to established a lock on the authority file, it failed to write
read the authorization file. the new changes. Verify that the file is in working
order and not corrupt.
User response: Ensure that there are sufficient system
resources available to read the contents of the
authorization file into a linked list. XVFB0055 ProgramName: creating new authority file
authority filename
XVFB0049 0: unable to parse displayname Explanation: The program is starting to create the new
authority file.
Explanation: The program was unable to parse the
given display name. User response: None.
User response: Verify that the display name in
question is correct and in the proper format. XVFB0056 ProgramName: unable to read auth
entries from file authority filename
XVFB0050 0: unable to get protocol address for Explanation: The program could not open the
displayname authority file for reading.
Explanation: The program was unable to parse out User response: When executing fopen against the
the protocol address for the given display name authority file, the program failed to establish a file
pointer. Verify that the file in question is not corrupt
User response: Verify that the display name in
and has the correct permission settings.
question is correct and in the proper format.

XVFB0057 ProgramName: unable to open tmp file

XVFB0051 ProgramName: unable to allocate len
filename
bytes for hexkey
Explanation: The program failed to open a new
Explanation: When attempting to malloc a space the
temporary file.
size of len, an error was encountered.
User response: When executing fopen, the program

8 z/OS V1.1.0 IBM Ported Tools for z/OS: Xvfb

was unable to establish a file pointer to a new that files containing Xauth help messages are available
temporary file. Verify the permission settings on the and not corrupt.
folder in which the file would live as well as verifying
there is sufficient disk space.
XVFB0064 on command user entered command
Explanation: A possible extension to an internal help
XVFB0058 ProgramName: filename not writable,
error message.
changes ignored
User response: If the user entered a command with
Explanation: The program was unable to write to the
the request for help, this message will be printed out.
file in question.
Verify that the command in question is a valid
User response: Verify that the file in question has the command and the Xauth help file containing this
correct permission settings. command exists and has the correct permissions.

XVFB0059 ProgramName: unable to write authority XVFB0065 no help for noexistent command user
file filename entered command
Explanation: The program was unable to write the Explanation: The user has requested help on a non
authority filem existent Xauth command.
User response: Verify that the file in question has the User response: Verify that the desired command was
correct permission settings and there is sufficient disk typed correctly and is a valid Xauth command.
space available.
XVFB0066 Commands:
XVFB0060 ProgramName: unable to link authority
Explanation: Header message for the help ?
file xauth_filename, use temp_name
command.
Explanation: When trying to establish links between
User response: None.
the temporary file and the new authority file, the
program encountered an error.
XVFB0067 unable to read any entries from file
User response: None.
filename
Explanation: No lines were read while trying to read
XVFB0061 unknown command user entered command
from the authorization file.
Explanation: The user has tried to enter an unknown
User response: The xauthorization file appears to have
command from the command line.
no data in it. Verify that there is in fact information
User response: Verify that the command given was within the file. If there is indeed data within, verify
typed correctly as well as a valid command. permissions on the file are correct.

XVFB0062 unable to open extraction file filename XVFB0068 digit entries read in: digit new, digit
replacement(s)
Explanation: Xauth was unable to open the file for
reading. Explanation: If merging entries with the verbose
option turned on, this message will print.
User response: The user has requested an extract
option from Xauth. While attempting to open the given User response: None.
filename for reading, the program encountered an error.
Verify that the file in question has the correct
XVFB0069 No matches found, authority file filename
permissions.
not written
Explanation: When executing the xauth option
XVFB0063 internal error with help
'extract', no matches for the given display could be
Explanation: Xauth encountered an error while trying found.
to process a help command.
User response: Verify that the display argument given
User response: The user has requested help for a to the xauth 'extract' command is a valid display.
given command. If a command was given at the
command line, the entered command will be displayed
after this message. If no command was given, this
message will be the only indication of the error. Verify

Chapter 2. Xvfb messages 9

XVFB0070 number entries written to filename XVFB0077 Authority file: authfilename OR none
Explanation: If the verbose option is turned on, this Explanation: Will print the xauthorization file name if
message will show after a successful xauth extract it exists. Will print none if not.
command.
User response: None.
User response: Information message only. Nothing to
be done.
XVFB0078 File new: Yes OR No
Explanation: If an xauthorization file existed, the
XVFB0071 key contains odd number of or non-hex
message will show No. If the xauthorization file has
characters
just been created, the message will show Yes.
Explanation: The key entered from the command line
User response: None.
is not in the correct format.
User response: Verify that the key was typed correctly
XVFB0079 File locked: Yes OR No
and is of the proper format.
Explanation: Displays the lock status of the
xauthorization file. If the ignore_locks flag is set, the
XVFB0072 unable to allocate number bytes for
message will print No, otherwise, Yes.
Xauth structure
User response: None.
Explanation: The program was unable to malloc
enough space for the Xauth structure.
XVFB0080 Number of entries: number
User response: Verify that there are sufficient system
resources available. Explanation: Will print the number of entries in the
xauthorization file.
XVFB0073 unable to allocate number character User response: None.
protocol name
Explanation: The program was unable to malloc XVFB0081 Changes honored: Yes OR No
enough space for the character protocol name.
Explanation: If the changes to the xauthorization file
User response: Verify that there are sufficient system were allowed, the status will show Yes, otherwise, No.
resources available.
User response: None.

XVFB0074 unable to allocate number bytes for auth

list XVFB0082 Changes made: Yes OR No

Explanation: The program was unable to malloc Explanation: If changes were made to the
enough space for the authorization list. xauthorization file, the status will show Yes, otherwise,
No.
User response: Verify that there are sufficient system
resources available. User response: None.

XVFB0075 unable to merge in added record XVFB0083 Current input: filename:linenumber

Explanation: When attempting to merge a new record Explanation: Displays the current input filename and
into the existing records, an error occurred. the line within the file.

User response: None. User response: None.

XVFB0076 number entries removed XVFB0084 line too long

Explanation: If the verbose option is enabled, this Explanation: The xauth command 'source' has found a
message will show how many entries were removed line within the specified file to be too long.

User response: None. User response: A command found within the file
passed to the source command is to long for the buffer.
Either reduce the length of the command within the file
(suggested) or increase the size of the buffer.

10 z/OS V1.1.0 IBM Ported Tools for z/OS: Xvfb

XVFB0085 unable to break line into words XVFB0092 unlink filename failed, errno number
Explanation: The xauth command 'source' has found a Explanation: The program failed to unlink the
line within the specified file that it is unable to parse. memory mapped file. An error number is given.
User response: A command found within the file User response: Use the provided error number to
passed to the source command is preventing the learn more about the specific failure.
program from correctly parsing the command. Verify
that there are no stray hidden characters within the file.
XVFB0093 shmdt failed, errno number
A common cause of this can be creating the file in a
windows environment and later moving this file to a Explanation: The program encountered an error while
*nix system. Also, verify that the file is in EBCDIC attempting to access shared memory. An error code is
format. given.
User response: use the provided error number to
XVFB0086 data contains odd number of or non-hex learn more about the specific failure.
characters
Explanation: While attempting to validate the key, an XVFB0094 Invalid screen number screen number
data format issue occurred.
Explanation: An invalid screen number has been
User response: Verify that the key was entered entered from the command line.
correctly.
User response: Verify that the command was entered
correctly and the entered screen number is within the
XVFB0087 unable to open display displayname. acceptable range.
Explanation: While trying to open the specified
display, an error occurred. XVFB0095 Invalid screen configuration entered
configuration
User response: Verify that the given display is a valid
display and any required connection is available. Explanation: An invalid screen configuration has been
entered from the command line.
XVFB0088 couldn't query Security extension on User response: Verify that the command was entered
display displayname correctly and the entered screen configuration is in the
correct format.
Explanation: While trying to query the Security
extension on the given display, an error occurred.
XVFB0096 Invalid pixmap depth number
User response: Verify that the display in question is
fully functioning and any required connection is Explanation: An invalid pixmap depth has been
available. entered from the command line.
User response: Verify that the command was entered
XVFB0089 couldn't generate authorization correctly and the entered pixmap depth is valid.
Explanation: xauth could not generate the required
authorization. XVFB0097 msync failed, errno number
User response: None. Explanation: While trying to flush any changes made
to the screens out to the mapped file, an error occurred.
XVFB0090 authorization id is number User response: Use the provided error number to
learn more about the specific failure.
Explanation: If the verbose option is set, this message
will show what the authorization ID is.
XVFB0098 open mapped filename failed, errno number
User response: None.
Explanation: The program failed to successfully open
the mapped file. An error code is given.
XVFB0091 ProgramName: unable to generate an
authority file name User response: Verify that user permissions on the
directory structure are correct. Also use the given error
Explanation: While trying to generate an authority file
code to learn more about the specific problem.
name, an error was encountered.
User response: Specify the name of an authority file
name from the command line with the -f 'filename'
argument.

Chapter 2. Xvfb messages 11

XVFB0099 write mapped filename failed, errno XVFB0106 failed to set default font path 'path to
number default font'
Explanation: The program failed to write to the Explanation: The program failed to successfully set
mapped file. An error code is given. the default font path.
User response: Verify that the user permissions on the User response: Verify that the program is attempting
directory structure are correct. Also use the given error to set the correct path.
code to learn more about the specific problem.
XVFB0107 Internal error in ConfigureWindow,
XVFB0100 mmap mapped filename failed, errno smode == number
number
Explanation: While internally organizing the window
Explanation: While trying to map pages of memory, stack, an error occurred.
an error was encountered. An error code is given.
User response: None.
User response: Verify that the user permissions on the
directory structure are correct. Also use the given error
XVFB0108 iop_disable failed (error condition)
code to learn more about the specific problem.
Explanation: While trying to disable the IOP Server,
an error was encountered. An error code is given.
XVFB0101 shmget number bytes failed, errno
number User response: None.
Explanation: While trying to allocate the given
amount of space in shared memory, an error occurred. XVFB0109 iop_getevents failed (error condition)
An error code is given.
Explanation: While polling the IOP server for events,
User response: Verify that user permissions on the an error occurred, preventing the query to happen.
directory structure are correct. Verify that there are
sufficient resources available for use. Also use the given User response: None.
error code to learn more about the specific problem.
XVFB0110 Couldn't open RGB_DB 'path to
XVFB0102 shmat failed, errno number RGB_DB'

Explanation: While trying to attach the allocated Explanation: The program could not open the given
shared memory to the process, an error occurred. An path to the RGB DB.
error code is given. User response: Verify that the program is trying to
User response: None. access the correct file.

XVFB0103 screen number shmid number XVFB0112 Value for "name" out of range: path:line
number
Explanation: Informational message of screen number
and shmid ID. Explanation: The given value for a color found in the
RGB config file is out of the acceptable range.
User response: None.
User response: Acceptable range is: red >= 0 And red
<= 0xff green >= 0 And green <= 0xff blue >= 0 And
XVFB0104 Internal Error! Attempt to remove a blue <= 0xff
non-existent device
Explanation: The program has attempted to remove a XVFB0113 Fatal server error:
non-existent device.
Explanation: Header that is printed any time a fatal
User response: None. error is encountered.
User response: None.
XVFB0105 FreeFontPath: FPE "length and name"
refcount is actual count, should be
expected count; fixing. XVFB0114 XDM: reason code, declaring session dead

Explanation: The expected and actual counter values Explanation: The session has been declared dead for
were found to be different. The program will the given reason code. This event typically happens
automatically adjust. because of too many timeouts or a failed keepalive
attempt.
User response: None.

12 z/OS V1.1.0 IBM Ported Tools for z/OS: Xvfb

User response: Try increasing the length of timeouts. file, looking for any erroneous characters or new lines.
Also check the status of any network communications.
XVFB0123 Couldn't open compiled keymap file
XVFB0115 XDM: too many retransmissions filename
Explanation: The program has reached the upper limit Explanation: While trying to open the keymap file
of retransmissions. listed, an error occurred.
User response: Increase the maximum limit of User response: Verify that the given file name is
retransmissions. correct and the file has the correct permission settings.

XVFB0116 XDMCP fatal error: type length.data XVFB0124 Error loading keymap filename
Explanation: A fatal error of the given type and length Explanation: While attempting to load the keymap
has occurred. The offending data is provided. file, an error occurred.
User response: Examine data section for clues to the User response: None.
cause of the error.
XVFB0125 Extra data (number bytes) after
XVFB0117 XDMCP warning: message SelectEvents
Explanation: An event of warning level severity has Explanation: Additional data was found after the
occurred. SelectEvent action.
User response: None. User response: None.

XVFB0118 Xserver: missing host name in command XVFB0126 BOGUS LENGTH in write keyboard
line desc, expected number, got number
Explanation: The program could not find a host name Explanation: The expected and actual values of the
from the command line. data length in the write keyboard description do not
match.
User response: Verify that the previous command line
entry was typed correctly. User response: None.

XVFB0119 Xserver: unknown host: unknown host XVFB0127 Internal error! Bad length in XkbSetMap
(after check)
Explanation: An unknown host name has been
entered from the command line. Explanation: The length found in XkbSetMap was
determined to be incorrect.
User response: Verify that that command was typed
correctly. User response: None.

XVFB0120 Xserver: host on strange network name XVFB0128 Internal error! Bad length in XkbSetMap
(after set)
Explanation: The program is alerting you to the
possibility of the host being misconfigured. Explanation: The length found in XkbSetMap was
determined to be incorrect.
User response: Verify that all settings are correct for
the host/server relation. User response: None.

XVFB0121 Unknown beep type number XVFB0129 Internal length error on read in
ProcXkbSetCompatMap
Explanation: The given number is of an unknown
beep type. Explanation: The length of a read in
ProcXkbSetCompatmap was incorrect.
User response: None.
User response: None.
XVFB0122 Error parsing config file:
Explanation: While parsing the XKB config file, an
error occurred.
User response: Verify that the contents of the config

Chapter 2. Xvfb messages 13

XVFB0130 BOGUS LENGTH in write names, XVFB0138 Internal Error! bad size (number!=number)
expected number, got number for _XKB_RULES_NAMES
Explanation: The expected and actual values of the Explanation: The expected and actual values for the
data length in the write names do not match. size of _XKB_RULES_NAMES were different
User response: None. User response: None.

XVFB0131 Unknown doodad type number in XVFB0139 Error loading keymap file filename (error
XkbWriteGeomDoodads code in location)
Explanation: The given doodad is unknown. Explanation: The program failed to successfully load
the keymap file.
User response: None.
User response: None.
XVFB0132 Ignored
XVFB0140 reverting to defaults
Explanation: The unknown doodad has been ignored.
Explanation: After a failed keymap file load, the
User response: None.
program will revert to the default values.
User response: None.
XVFB0133 BOGUS LENGTH in XkbSendGeometry,
expected number, got number
XVFB0141 Error opening keymap file filename,
Explanation: The expected and actual values of the
reverting to defaults
data length in XkbSendGeometry do not match.
Explanation: The program failed to successfully load
User response: None.
the keymap file. The default values will be reinstated.
User response: None.
XVFB0134 Internal Error! bad
RemoveResourceClient in
XkbClientGone XVFB0142 Internal Error!! XKB and core keymap
have different range
Explanation: An error occurred while trying to
remove a resource client. Explanation: XKB and the core keymap have been
found with different ranges.
User response: None.
User response: None.
XVFB0135 Attempt to change unknown pointer
default (number) ignored XVFB0143 Couldn't load XKB keymap, falling back
to pre-XKB keymap
Explanation: The program has ignored the request to
change the default pointer type to an unknown type. Explanation: Tried to load an XKB keymap file. This
action failed and the previous settings will be used.
User response: None.
User response: None.
XVFB0136 Atom error: atom not created
XVFB0144 InternalError! Illegal radio group number
Explanation: The specified atom was not created.
Explanation: XKB tried to process an illegal radio
User response: None.
group.
User response: None.
XVFB0137 Allocation error: atom property not
created
XVFB0145 unknown key behavior 0xbehavior type
Explanation: When trying to allocate the given atom,
an error occurred. Explanation: An unknown key behavior type has
occurred. This typically indicates an error with the
User response: None.
keyboard. Typical key behavior includes pressed or not.
User response: Verify that no keys are stuck and the
keyboard is functioning properly.

14 z/OS V1.1.0 IBM Ported Tools for z/OS: Xvfb

XVFB0146 Extra data (number bytes) after XVFB0154 bogus pointer event from ddx
SelectEvents
Explanation: The pointer received is invalid.
Explanation: Extra data was found after the
User response: None.
SelectEvents action.
User response: None.
XVFB0155 client not on event list
Explanation: The program could not find a given
XVFB0147 Internal Error! Bad XKB info in
client within the previously configured client list.
SetPhysicalLockingKey
User response: Verify that all clients are listed and
Explanation: While reading the
you are trying to connect to a client on the list.
SetPhysicalLockingKey, bad information was found
contained within.
XVFB0156 failed to allocate spriteTrace
User response: None.
Explanation: While attempting to xalloc space, an
error occurred.
XVFB0148 MAXFORMATS is too small for this
server User response: Verify that there are sufficient system
resources available.
Explanation: The current setting of MAXFORMATS is
too small.
XVFB0157 Not implemented
User response: Increase the level of MAXFORMATS
Explanation: Informational message which
accompanies additional messages when an as yet
XVFB0149 Couldn't add screen number
unimplemented function or feature is called.
Explanation: XVFB could not add the given screen.
User response: None.
User response: None.
XVFB0158 server restarted. Jumped through
XVFB0150 initializing atoms uninitialized pointer?
Explanation: Informational message. The program is Explanation: The server has been restarted. The most
initializing atoms. typical cause of this is from jumping through an
uninitialized pointer.
User response: None.
User response: None.
XVFB0151 SetMaskForEvent: bogus event number
XVFB0159 couldn't create client array
Explanation: The found event number falls outside
the acceptable range. Explanation: While trying to xalloc space for an array,
an error occurred.
User response: None.
User response: Verify that there are sufficient system
resources available.
XVFB0152 SetCriticalEvent: bogus event number
Explanation: The found event number falls outside
XVFB0160 couldn't create server client
the acceptable range.
Explanation: While trying to xalloc space for an array,
User response: None.
an error occurred.
User response: Verify that there are sufficient system
XVFB0153 Impossible keyboard event
resources available.
Explanation: The program encountered an unexpected
keyboard event.
XVFB0161 couldn't init server resources
User response: Restart the server and try again.
Explanation: While trying to initialize resources for
the root resources, an error occurred.
User response: None.

Chapter 2. Xvfb messages 15

XVFB0162 couldn't create root window table XVFB0171 could not open default font 'font name'
Explanation: While trying to xalloc space, an error Explanation: The program could not open the default
occurred. font listed.
User response: Verify that there are sufficient system User response: Verify that the specified font file exists
resources available. and has the correct permissions.

XVFB0163 no screens found XVFB0172 could not open default cursor font 'font
name'
Explanation: The program was unable to find any
active screens. Explanation: The program could not open the default
cursor font.
User response: None.
User response: Verify that the specified font file exists
and has the correct permissions.
XVFB0164 failed to allocate serverClient
devprivates
XVFB0173 could not create connection block info
Explanation: The program failed to allocate
serverClient devprivates. Explanation: The program failed to create connection
block info.
User response: None.
User response: None.
XVFB0165 failed to create scratch pixmaps
XVFB0174 FakeClientID: server internal ids
Explanation: The program failed to create scratch
exhausted
pixmaps.
Explanation: All possible ID's have been assigned.
User response: None.
User response: Restart the server.
XVFB0166 failed to create screen resources
XVFB0175 client not in use
Explanation: The program failed to create screen
resources. Explanation: When attempting to add a resource, the
target client was found to not be in use.
User response: None.
User response: Ensure that the correct client is trying
to be utilized.
XVFB0167 failed to create scratch GCs
Explanation: The program failed to create scratch
XVFB0176 Freeing resource id=ID which isn't there
GCs.
Explanation: The program attempted to free an ID
User response: None.
which does not exist.
User response: None.
XVFB0168 failed to create default stipple
Explanation: The program failed to create default
XVFB0177 could not create root tile
stipple.
Explanation: The program could not initialize the
User response: None.
required root tile.
User response: None.
XVFB0169 failed to create root window
Explanation: The program failed to create root
XVFB0178 Failed to establish all listening sockets
window.
Explanation: The program failed to establish all the
User response: None.
expected listening sockets.
User response: Verify that the network connection is
XVFB0170 failed to initialize core devices
working properly. Use a tool such as netstat to verify
Explanation: The program failed to start necessary which ports are open and currently listening.
core devices.
User response: None.

16 z/OS V1.1.0 IBM Ported Tools for z/OS: Xvfb

XVFB0179 Cannot establish any listening sockets - XVFB0186 Error reading option file filename
Make sure an X server isn't already
Explanation: The program cannot open the given
running
option file.
Explanation: The program failed to create any
User response: Verify that the file name is correct and
listening sockets.
the file exists with the correct permissions.
User response: Verify that an existing instance of an X
server is not running.
XVFB0187 Out of memory reallocing option buf
Explanation: While attempting to reallocate space for
XVFB0180 No hostname, no screen
a buffer, an error occurred.
Explanation: When trying to get the IOP server
User response: Ensure that there are sufficient system
capability and start it, an error occurred.
resources available.
User response: Verify that the correct hostname and
screen ID have been used.
XVFB0188 Out of memory
Explanation: The program has run out of memory
XVFB0181 Cannot find IOP server for server
hostname: error code User response: Verify that the system has sufficient
memory available.
Explanation: The program cannot find the IOP server
for the listed hostname. An error code is provided.
XVFB0189 Couldn't allocate keyboard controls
User response: Ensure that the given hostname is
correct. Also use the given error code to find more Explanation: The program failed to allocate the
information on the specific error. keyboard controls.
User response: Ensure that there are sufficient system
XVFB0182 iop_enable failed (error string) resources available.
Explanation: While trying to enable the IOP server, an
error occurred. An error code is provided. XVFB0190 Couldn't allocate keyboard description
User response: Use the given error code to find more Explanation: The program failed to allocate the
information on the specific problem. keyboard description.
User response: Ensure that there are sufficient system
XVFB0183 Cannot start IOP reader thread resources available.
Explanation: While attempting to start the thread used
to read information from the IOP server, an error XVFB0191 Couldn't allocate client map in
occurred. XkbInitDevice
User response: Restart the server. Explanation: The program could not allocate client
map in XkbInitDevice.
XVFB0184 Can't open option file filename User response: Ensure that there are sufficient system
resources available.
Explanation: The program cannot open the given
option file.
XVFB0192 Couldn't allocate server map in
User response: Verify that the file name is correct and
XkbInitDevice
the file exists with the correct permissions.
Explanation: The program failed to allocate server
map in XkbInitDevice.
XVFB0185 Out of Memory
User response: Ensure that there are sufficient system
Explanation: The program has run out of memory.
resources available.
User response: Verify that the system has sufficient
memory available.
XVFB0193 Couldn't allocate keysyms
Explanation: The program couldn't allocate keysyms.
User response: Ensure that there are sufficient system
resources available.

Chapter 2. Xvfb messages 17

XVFB0194 Couldn't allocate modifierKeyMap in
UpdateCore
Explanation: The program failed to allocate
modifierKeyMap in UpdateCore.
User response: Ensure that there are sufficient system
resources available.

XVFB0195 Couldn't allocate symbols map in

UpdateCore
Explanation: The program failed to allocate symbols
map in UpdateCore.
User response: Ensure that there are sufficient system
resources available.

XVFB0196 could not add Xie as an extension

Explanation: While attempting to add Xie as an
extension, an error occurred.
User response: None.

18 z/OS V1.1.0 IBM Ported Tools for z/OS: Xvfb

Notices
This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
USA

For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan

Programming Interface Information

This publication documents intended Programming Interfaces that allow the
customer to write programs that use Open Source Tools for z/OS.

Trademarks
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered
trademarks or trademarks of Adobe Systems Incorporated in the United States
and/or other countries.

Other company, product, and service names may be trademarks or service marks
of others.

© Copyright IBM Corp. 2010 19

20 z/OS V1.1.0 IBM Ported Tools for z/OS: Xvfb
Accessibility
Publications for this product are offered in Adobe Portable Document Format
(PDF) and should be compliant with accessibility standards. If you experience
difficulties when using PDF files, you may view the information through the z/OS
Internet Library Web site or the z/OS Information Center. If you continue to
experience problems, send an e-mail to [email protected] or write to:
IBM Corporation
Attention: MHVRCFS Reader Comments
Department H6MA, Building 707
2455 South Road
Poughkeepsie, NY 12601-5400
U.S.A.

Accessibility features help a user who has a physical disability, such as restricted
mobility or limited vision, to use software products successfully. The major
accessibility features in z/OS enable users to:
v Use assistive technologies such as screen readers and screen magnifier software
v Operate specific or equivalent features using only the keyboard
v Customize display attributes such as color, contrast, and font size

Using assistive technologies

Assistive technology products, such as screen readers, function with the user
interfaces found in z/OS. Consult the assistive technology documentation for
specific information when using such products to access z/OS interfaces.

Keyboard navigation of the user interface

Users can access z/OS user interfaces using TSO/E or ISPF. Refer to z/OS TSO/E
Primer, z/OS TSO/E User's Guide, and z/OS ISPF User's Guide Vol I for information
about accessing TSO/E and ISPF interfaces. These guides describe how to use
TSO/E and ISPF, including the use of keyboard shortcuts or function keys (PF
keys). Each guide includes the default settings for the PF keys and explains how to
modify their functions.

z/OS information
z/OS information is accessible using screen readers with the BookServer or Library
Server versions of z/OS books in the Internet library at:
http://www.ibm.com/systems/z/os/zos/bkserv/

© Copyright IBM Corp. 2010 21

22 z/OS V1.1.0 IBM Ported Tools for z/OS: Xvfb
Index
A
accessibility 21

D
disability 21

I
IBM Ported Tools for z/OS
publications
on CD-ROM v
softcopy v

K
keyboard 21

N
Notices 19

P
publications
on CD-ROM v
softcopy v

S
shortcut keys 21

X
Xvfb
command description 1
messages 5

© Copyright IBM Corp. 2010 23

24 z/OS V1.1.0 IBM Ported Tools for z/OS: Xvfb



Program Number: 5655-M23

Printed in USA

SA23-2216-00