|

Q: When I attempt to
use the Celview printer application and connect to an AS/400, the
session window in Celview Printer displays a message
"Could not use the session because creation of device failed." How do
I fix this?
A: Open the configuration
for that printer session in the Celview configuration editor. The "Printer Name"
specified there must be the same as a printer device configuration file for
that user on the AS/400. This name is set by the AS/400 administrator.
The actual configuration on the AS/400 of the printer device must include
the following settings: "device class = *vrt"; "device type = 3812"; "option = *basic";
"advanced function printing = no".
Q: On Mac OS 10.3.x,
I cannot use the F9, F10,or F11 keys in Celview. Why?
A: New on Mac OS 10.3 (Panther) is
"Expose". It uses these keys, but you can change that thru the System Preferences.
An alternative, in Celview, is to trigger the functionality of those keys thru
a Celview Quickpad. Or one can use the Celview keyboard mapping to remap the
functionality of those keys.
Q: With the multiple keyboard feature in Celview 3.0.3,
I do not see the keyboards I am expecting. Why?
A: All Apple keyboards should correctly
identify themselves. In a small number of situations, such a keyboard may give you a choice of which screen keyboard
to use in mapping keys. Non-Apple USB keyboards will usually identify themselves as an Apple Extended Keyboard.
That is the situation under the carbon version of Celview 3.0.3. We recommend you use the carbon version
where possible.
With the classic version, running in classic on Mac OS X, one will see no keyboards.
Use the carbon version! Also running OS versions pre 8.6, one will not see some USB keyboards. Sorry!
Q: When I
try to print on Mac OS 10.2.4 or later, either it just does
not print or I get a postscript error. Why?
A: With 10.2.4
and up, for some networked postscript printers, the
Noiro font causes a postscript error. This will even happen using
Noiro
in TextEdit. The new
version of Noiro available from our downloads
page
fixes this for most users. If one prints in Courier or another font, the problem
does not exist.
For users who are not helped by the above font
update, they should update their printer drivers to the latest version for the
specific printer. If that still does not fix it, then download the free open
source printer drivers from
Gimp-Print. We know Gimp-Print 4.2.6 and later will fix the problem for at least
some, if not all, printers.
Updating to Mac OS 10.3.x (Panther) will
also update the printer drivers, and this can fix the problem too.
Q: When I
run Celview 3.0 or 3.0.1 on Mac OS X 10.2 ("Jaguar") Celview
sometimes crashes. Why?
A: There is
a bug in Mac OS 10.2 and 10.2.1 that can crash Celview in the
first minute after it is launched. The crash is erratic and on
some systems may not occur. Celview 3.0.2 fixes this.
Q: I get
the message "Couldn't connect the session because the connection
tool couldn't be opened.". Why?
A: Most likely
this is caused by an improper KeyCode. Try re-entering it. Note
that you have to enter it, then quit Celview and re-launch it.
Q: My function
keys do not work in Celview.
A: On classic
Macintosh, go to the "Keyboard" control panel and press
the "Function Keys ..." button. Then make sure that
the check box is set so that the function keys work as function
keys and not as hot keys.
On Mac OS
9.1 and later that check box is turned on by default so that the
function keys serve as hot keys. That must be turned off.
On Mac OS
X go to the "System Preferences" application and bring
up the Keyboard preferences. Then adjust settings there.
Q: The F12
function key does not work.
A: Right.
This ejects the CD/DVD tray. We cannot override Apple's use of
this, so we suggest that you use Celview's keyboard mapping to
assign the F12 functionality to some other key. A similar problem
affects a small number of other keys also. With Mac OS X 10.1.3,
if the F12 key is pressed for less than 1/4 second it will actually
work as an F12 key.
Q: When I
try to start the Celview SNA Gateway, it starts, but then it does
not connect to our AS/400.
A: There are
two common causes for this. In the Gateway Admin application,
select a gateway on the network in the "Network Gateway Status"
window. Then go to the Gateway menu and select the "Change
Settings ..." menu item. Make sure that the selected gateway
has a name that is at least two characters long, and that it is
a unique gateway name on the local appletalk zone. (That is the
first cause.)
You may also
wish to turn on the "Autostart this Gateway" checkbox
in the "Change Gateway Settings" dialog box.
Then go back
to the "Network Gateway Status" window and use the Gateway
-> Start Gateway menu item to start that gateway. Once it is
started double click on the gateway name in that window and a
Gateway Resource window will come up.
Select the
Mode that you are using to connect, and then use the Resource
-> Activate Mode menu item, to activate the mode. The list
of sessions for that mode should appear with black dots beside
them to indicate that they are active. (This is the second cause.
Also see the next question.)
Q: The autostart
option in the "Change Gateway Settings" dialog box does
not work for connecting to our AS/400.
A: Yes, this
is a bug in Celview 3.0 at the time of its release, when Celview
tries connecting to OS/400 V4 and V5. We have this on our high
priority list for fixing.
Q: When
I print, using the Celview AS400 Printer application, every page
gets split between two printed pages.
A: This is
due to the AS/400 (and the mainframe also) requesting a page size
that is not compatible with what is set on your Macintosh with
the "Page Setup ..." menu item in Celview. The page
length on the Macintosh is shorter then what the AS/400 wants,
with the result that every page is split. Change the page size
in the "Page Setup ..." dialog box.
Q: The mainframe
wants to print in landscape mode, but Celview Mainframe Printer
does not automatically switch to landscape.
A: Yes this
sometimes happens. Just use the "Page Setup ..." dialog
box. We have tried to make available as much as possible of the
Macintosh printing flexibility.
Q: My Macintosh
goes to sleep with a connected session live. When it wakes up, the
session is disconnected and the cursor is the rotating beach ball.
A: This is
known to happen on Mac OS X with sessions using the 3270GC and
5250GC connectors. When the Macintosh goes to sleep, the operating
system can put the networking to sleep too and no "tickle"
packets will be sent. Two minutes later the other end of the connection
decides the connection is dead and terminates its end. When your
Macintosh wakes up, it does not know the other end has terminated,
and it will take about 20 seconds to figure that out. During that
time the beach ball cursor will be rotating.
Q: I want
to automatically connect to our AS/400 (or mainframe) and go to
a specific screen. How do I do it?
A: Connect
to the AS/400 and save a session document for that session. Then
go to the Macro menu and turn on Start Recording. Navigate to
the screen. Stop the macro and save it.
Use the "Session"
menu -> "Macros" menu item and assign the macro to
the Automatic Connection item. Save the session. This setting
will be saved with the session document. When you double click
on the session document the macro will fire automatically.
Note that
one can refine the macro using appropriate pause commands, where
there may be a delay with some screens coming up. Check the Celview
documentation.
Q: The mainframe
(or AS/400) screen displays a table with columns and rows. How can
I cut and paste this into a spreadsheet?
A: You need
to use a Custom Clipboard Format. Go to the File menu and select
"New Other ...". Then press the Clipboard Format radio
button and press OK.
In the window
that comes up, press the "As a Table Separated by:"
radio button, and under that the "Columns of Blanks"
radio button. Then set it to have a "Return" character
after every row, and a "Tab" character in between columns.
Save the format document to an appropriate location (see below).
When you go
to do the copy and paste, select the table in the screen as a
rectangular area, and use the "Edit" -> "Copy
Formatted" menu item with the format document you have just
saved.
Note that
Celview can show Format documents, as well as macro and keypad
documents, in its menus, making them easy to access. It has to
know how to find them, and one uses the Celview preferences for
this.
The Celview
preferences window has an area entitled "Document Search"
which has a number of options. One can put the documents in the
application folder, the Celview preferences folder or the Documents
folder, or they can be found indirectly thru a folder alias in
one of those folders. Documents saved in those locations will
be found and shown in the Celview menus.
Q: The Celview
session screens update slowly when I switch applications or windows.
Why?
A: You have
a lot of documents in the "Document Search" locations
mentioned above. Reduce the number of documents in the search
path.
Q: The "Display
Settings" dialog box reached from "Session" ->
"Display ..." allows me to change the display font, but
it only shows one font. How do I change this?
A: You don't!
The Noiro font has special characteristics that enable its use
for displaying AS/400 and mainframe screens - it is a monospace
font and its bold version is also monospace of exactly the same
size. There are very few fonts that have those properties.
This dialog
box also allows one to change the print screen font. While you
can change this, you probably do not want to for the same reason.
Q: I want
to automatically collect the data in from a number of fields in
certain screens on our AS/400 (or mainframe). This is something
that I will likely have to do again and again. Can I automate this?
A: Yes. At
least, probably, since it depends on exactly what you are doing.
In general terms, you probably want to create a session document
and attach a startup macro to it. Screen navigation will be controlled
by macros or applescripts. There are examples of this in "Sample
Celview Documents". Data copying from fields is done by using
applescripts, and there is a very brief example at the end of
the document "More Celview Macros and Scripts". Timeouts
can be controlled with applescript timeouts.
Q: PC Support
file transfer does not seem to work. Why?
A: PC Support
uses the Celview SNA Gateway Components, which are a custom install
from the Celview installer. They must be installed.
|