Reference: F00018935
The process would be to compile programs with TGTRLS(V3R1M0) (or
whatever target release you wish), then SAVxxx with same TGTRLS(). The
conversion of programs occurs on the CISC system during the restore
operation (which can take considerable time).
Alternatively, you could do your SAVxxx TGTRLS() to a save file,
then SAVOBJ TGTRLS() the save file to tape. Then when you restore the
savf object to the target system, no conversions would occur until you
RSTOBJ out of the save file. This would let you separate the tape time,
from the program translation time. Then your tape drive will be free
for any other operations you may wish to perform.
Reference: F00018936
For devices there is usually only one bit on in the kind3. For
IOPs and IOAs there are frequently several bits on because an
IOP may support communications, tape, diskette, DASD, and workstations
at the same time.
You might perform a logical AND operation on the kind value with the
constant you are checking for and then compare for non-zero result.
Reference: F00018937
If power was not available to the system at the time the IPL was
scheduled to be performed, then it will occur once power is restored.
Whether that is 10 minutes later, or the next day. Since you scheduled
an IPL, the system tries to IPL for you, as soon as it can. So, in the
case where you plug it in a day after the original scheduled IPL date,
the system should IPL for you. This will be the same on RISC and CISC.
To confirm the reason the system has IPL'd, check the QIPLSTS system
value. A value of 3 indicates the IPL was triggered by the QIPLDATTIM.
Reference: F00018938
For more information about how to try and improve the performance of
such an application, you will want to review the AS/400 Client/Server
Performance using the Windows 3.1 Client SG24-4526. Now I realize you
probably are using Win95, but most of the concepts discussed are the
same in both environments.
If you have not yet reviewed the basic database performance of your
server application and you are doing ODBC, you may want to start by
studying your database requests. This can be done with STRSRVJOB on
your ODBC host server job (once you connect with ODBC) and then STRDBG.
Then just run one of your queries, and the query optimizer will place
detailed messages in the joblog describing how it has resolved the
query. A common cause of poor performance occurs when the query
optimizer is forced to build it's own access paths over large physical
files. You can avoid this by creating the appropriate access paths over
the files ahead of time. The joblog will show you the access path that
it recommends you build for it.
Reference: F00018939
Another option (more work), might be to have the program(s) that are
manipulating the records store the rec # in a common area somewhere (a
user space, data area, shared memory, etc.) where the trigger could
retrieve it. This still wouldn't handle cases like updating a record
via ODBC or DFU etc. but would at least handle changes made elsewhere
in your application.
Hope this helps. You might want to make a formal request for such
function with your local branch office.
Reference: F00018940
This "pseudo" program opens a queue, writes 10 messages to the queue and
then reads them back. It reads them back using timed async reads. It
does a priming read, immediately does a checkdata to see if there
was data, and then enters a loop. If checkdata returned no data or
returned ok, it immediately starts the next async read and then processes
the one just read. If the processing program fails, we cancel the
previous read and exit the loop.
main()
cwbDQ_Data data1 = cwbDQ_CreateData()
cwbDQ_SetDataAddr(data1, buf1, sizeof(buf1))
memset (buf1, 'A',sizeof(buf1));
if (rc != CWB_OK)
rc = cwbDQ_AsyncRead(data1, &read1,10)
Reference: F00018941
Upgrading from a CISC system, in your case V3R2 to a RISC system,
V4R1 requires a lot of planning in order for the upgrade to be
successful. If you have not already gone through it, I strongly
recommend that you reference the AS/400 Road Map for Changing to PowerPC
Technology, Publication Number: SA41-5150. In this book, it talks
about everything that is necessary to do in preparation for your
upgrade. You can find this manual on the Internet at:
Will the DUPTAP command work after RISC to CISC conversion?
A:
If the tape you start with is not
restorable to the CISC system, then the copy you make will not restore
either. DUPTAP does not alter the data. It is a block for block copy.
How do I retrieve a list of disk drives?
A:
The "kind" values are bit encoded.
To find all DASD devices: check that the device bit is on in the
kind1 value and the DASD bit is on in the kind3 value.
What is the correct way to read QIPLDATTIM?
A:
When the QIPLDATTIM system value is changed, it is sent down in to
the service processor hardware (in the control panel of the system
where the system clock and little batteries are). The service processor
is what is responsible to bring the system back up.
How do I measure client-server performance?
A:
There is no easy answer to your question. You have pretty clearly
pinpointed one of the most difficult things to measure in a client/server
environment. You can use a communications trace to get timestamps for
when requests are received, and when results are returned. This would
tell you the time spent on the AS/400 side to service a request. The
rest of the client's response time would include the networking delays,
and delays on the PC side in processing the data. You could also use
performance tool reports to review the CPU time used and I/O performed
in your host server job. If you run the same type of requests
repeatedly, then you could get an average for each transaction of that
type.
Is there any way to retrieve the record number of the processed record?
A:
No, there really isn't. If you are talking about a before change
trigger, then the program updating the record would still be holding a
lock on that record, and thus you could tell by that which record
number caused the trigger. Other than that, it would appear you will
have to use the key to the record rather than record number.
How does cwbdb_cancel work?
A:
We don't have a fully
functional example using cwbdb_Cancel, however, here is
a simple
"pseudo" program that you could finish that would use a cancel.
{
int rc = cwbDQ_Open(...)
// Open the queue
cwbDQ_Data data2 = cwbDQ_CreateData()
cwbDQ_Data currData = 0
// currently used data object (handle)
cwbDQ_Data nextData = 0
// next free data object (handle)
cwbDQ_ReadHandle read1 = 0
// Async
read handle
// Set up our buffers
cwbDQ_SetDataAddr(data2, buf2, sizeof(buf2))
// Fill buf1 with something
{
}
// Do a priming read with a 10 second wait
rc = cwbDQ_CheckData(read1)
currData = data1
nextData = data2
int count = 0;
while(rc == CWBDQ_NO_DATA || rc == CWB_OK && count < 10)
{
{
}
What PTF tapes are need to upgrade from V3.2 to V4.1?
A:
If you are referring to the Upgrade Assistant PTFs, there are none
for V4R1. It is in the base operating system now. All other required
PTFs are described in the Upgrade Roadmap (see below). And there is a
PSP PTF for the book itself, which is SF98152.
You should also order and read the following:
| PTF | SF98010 - | Preventative Service Planning (PSP) Information |
| SF98151 - | Software Installation Planning Information for R410 | |
| SF98016 - | Read this First and Memo To Users |
Reference: F00018942
If it becomes necessary, you may want to contact your marketing rep, requesting
an RPQ from Tucson to determine whether or not we would be able to perform a model
conversion for you on a special bid basis.
Reference: F00018943
Reference: F00018944
Which media controllers support which models?
A:
The #2621 Removable Media Device Attachment controller supports the
model A43 and the model S40.
The problem comes in with
the PCI technology systems like the model 600. I have some notes
that indicate the next release of OS/400
will support Direct-Attach models. Announcement letter 198-029
confirms that 3995s can be attached via the #2729 PCI Magnetic Media
Controller at V4R2.
How can I display current users of Client Access?
A:
The WRKLICINF command will display the registered
licensed program products. Roll down to 5769XW1 and use option
8 = Work with license users. This will display the names of all the jobs
that are holding one of the concurrent licenses.
How do I retrieve diagnostic messages via ODBC?
A:
Your client application will obviously want to trap the exception.
Once an exception is trapped, you could call a stored procedure. This
is just a native AS/400 program, defined to ODBC with CREATE PROCEDURE.
It will be running from the same ODBC server job that was running when
the trigger reported the failure msg. So, write a stored procedure that
retrieves the error message placed in the joblog by the trigger and
return it to the client application. This stored procedure could be a
CL program which uses the MSG commands to retrieve the joblog msgs. Or,
you could use the Message Handling APIs documented in the System APIs
Reference. Or, see the section entitled OS/400 Message Handling APIs in
softcopy or on the web at:
Reference: F00018945
From the RFC: Therefore, I suggest that you allow the initial connection to complete. Then your client application can issue
the DONT ECHO command, and by protocol definition, the AS/400 MUST honor this.
Reference: F00018946
How do I setup a local Echo on the AS/400?
A:
Please refer to RCF 857 for complete details on the ECHO option negotiation sequences.
The AS/400 should accept a DONT response, yet continuing this request is not
in violation of the RCF. However, the RFC clearly states that if the sender sends a DONT ECHO
request, the receiver MUST honor this request.
How do I send a program message from a trigger program?
A:
There is a redbook called DB2/400 Advanced Database Functions GG24-4249 in the ITSO section of
the following website:
It describes the details of how to send failure messages back to the program that originally wrote the record. The QMHSNDPM API is used to send a program message. An example is shown of delivering a msg to the user from the application that caused the record update whose trigger fails for some reason.
If it helps you on your way any faster, the example shows passing the call stack parameter with a binary value of 1. If you are coding in ILE/RPG, don't forget that a binary 4 field is defined with length 9 in the D specs (unless you define both a starting and ending position, in which case you would want positions that span four bytes).
The system will send a CPF502B that the trigger failed, in addition to any program messages you send in your application.
Reference: F00018947
You can view this book directly on the web at:
Where do I find CPW numbers for a non-server AS/400?
A:
The marketing information has these details. On a non-server system,
there is only one CPW figure. Batch and interactive both run normally
with no degradation. The best source to get all these figures in one
place is probably the AS/400e series System Handbook GA19-5486-15.
There is a link at the bottom of the front page for the System Handbook.
Reference: F00018948
C DRIVE:
Contains the programs needed for booting. This drive MUST remain
formatted as FAT. It is 10 MB in size and resides on QUSRSYS library.
D DRIVE:
Holds a copy of the Windows NT install code and a copy of the AS/400
integration with Windows NT code. This is 200 MB and resides in QUSRSYS
library.
E DRIVE:
This is the Windows NT system drive which is 500 MB and holds the copy
of the installed version of Windows NT and the AS/400 integration code.
This resides in the QUSRSYS library and is initially formatted as FAT,
however, it is recommended that this drive be reformatted to NTFS
(which is done from the Windows NT console. At a MS-DOS prompt, enter the
command CONVERT E; /FS:NTFS.
Additional storage spaces can be manually created (using the CRTNWSSTG command) and linked
to the server. These will reside in the IFS in the root directory under the /QFPNWSSTG directory.
Reference: F00018949
Client Access/400 for Windows 3.1
The Client Access/400 for Windows 3.1 client supports the
following TCP/IP stacks. To use these stacks listed below,
refer to Informational APAR 1108755 for any required PTF
numbers that must be installed on the AS/400 system.
Note: Unpredictable results may occur with unsupported
TCP/IP stacks.
Note: 3.11a applies to the TCP/IP stack and 3.11 applies to
the WFW.
The TCP/IP stack must be installed and running before Client
Access/400 for Windows 3.1 can run over AnyNet® for OS/2. A
communications-stack-only version of IBM TCP/IP for DOS is
sent along with Client Access/400 for Windows 3.1, which can
be found either on the AS/400 tools folder (QIWSTOOL) or on
the communications diskettes, feature number 8540. For
information on how to create the diskettes, see page 2-3 of
the Client Access/400 for Windows 3.1 User Guide, SC41-3532
Note: To create the diskettes from the tools folder, you
must have cumulative tape number C5227310 (Julian date 227)
or PTFs SF32551, SF32552, and SF32553 for product 5763-XA1.
Client Access/400 Optimized for OS/2
There are some special considerations for the setup between
the AnyNet support provided with Client Access/400 Optimized
for OS/2 and TCP/IP. See the Communications Configuration,
SC41-3401 and the README.CA4 file sent with the Client
Access/400 Optimized for OS/2 for information on setting up
APPC (SNA) over TCP/IP. Later this year (fourth quarter
1995), a Redbook will be available with helpful information
for setting up Client Access/400 Optimized for OS/2 with
AnyNet and TCP/IP. Its order number will be GG24-2587.
Reference: F00018950
Reference: F00018951
Generally, the automatic and manual installation methods do
not install new licensed programs or new optional parts.
New can have either of the following definitions:
The licensed program or optional parts have been available
but are considered new because they are being added to your
system for the first time.
The licensed programs or optional parts have just been
introduced for the first time. The new licensed programs
can be introduced with a new release of the operating system
or independently of it.
For either definition, new licensed programs and new
optional parts are installed using the procedure for
installing additional licensed programs in the Software
Installation book.
Note:
Occasionally, exceptions are made so that new licensed
programs or options install if they replace an installed
product that is no longer supported. Be sure to read any
associated information about new licensed programs you
intend to install.
Reference: F00018952
The following are general V3R1 performance considerations
and recommendations.
For example, on an F50 the acceptable range is 25-50
faults/second. If the faulting rate is at 45 per second,
you should consider more main storage for V3R1.
This is specially important for 8MB systems and for systems
with a large number of Client Access/400 or communications
jobs.
First IPL after installing V3R1
You should ensure these jobs are in the DEQW (dequeue wait)
state before starting production work after the first IPL:
Additionally, many of the IBM-supplied products, such as
Client Access/400 and TCP/IP, run jobs in subsystems
QSERVER, QCMN, and QSYSWRK. These subsystems are shipped to
run jobs in storage pool *BASE for ease of installation.
However, you must consider enlarging *BASE storage pool or
changing the subsystem descriptions to run these jobs in
separate storage pools.
Reference: F00018953
Do not use the QPFRADJ value and the SETOBJACC command at
the same time for a shared pool. QPFRADJ removes storage
from a shared pool that has not paging activity. If the
SETOBJACC command is used to preload an object into the same
pool, it may lose some of its storage. The SETOBJACC
command is used to cause no page faulting to occur in the
pool, and QPFRADJ would consider that pool a prime candidate
for removing storage.
In some cases, QPFRADJ at IPL should not be used because IPL
tuning can undo acceptable performance that is achieved by
dynamic tuning or manual tuning done during normal system
operation. In an environment with the same number of active
jobs and no new applications, QPFRADJ is set to 0 after it
has been used to obtain optimal paging rates across the
system.
Reference: F00018954
Reference: F00018955
Note: Direct LAN attachment of printers for OS/400 printing
is supported only on Version 3 Release 1.0 or higher. PTF
SF2177B should be applied.
The 4033 External Print server must have a SSAP parameter
value of 12.
The MarkNet XLe External Print Server must have the SSAP
parameter values of 12, 16, and 1A.
For More Information
Reference: F00018956
A cumulative PTF package contains PTFs that fix frequently
reported problems since the start of a release. For V3R1 or
earlier releases, cumulative PTF packages can be ordered
electronically or by telephone and are always sent by mail
on a tape.
Reference: F00018957
Full details on all of these changes can be found in the
TCP/IP Compatibility Newsletter, SC41-0191. You are
strongly encouraged to study the newsletter thoroughly.
Studying the newsletter will enable you to be prepared for
and to take advantage of the new V3R1M0 TCP/IP
implementation.
Reference: F00018958
If a single job is hung up, decide what to do based on the
status of the job and its function. You can use the Work
with Active Jobs (WRKACTJOB) display to watch the job and
see if it is hung up or in a continuous loop (when you use
the refresh function, does the status change?). Check for
messages about the job. You may need to end the job, which
you can do from the Work with Active Jobs display. You can
also end a job by using the End Job (ENDJOB) command or the
End Job Abnormal (ENDJOBABN) command.
If your entire system is hung up, you probably need help
from software support (1-800-274-0015). Collect the
following information before you call so that software
support can help you more quickly:
Appendix B in the System Startup and Problem Handling has
forms and instructions that you can use to capture the right
information before you call.
Reference: F00018959
How long has it been since your last IPL? Longer than
usual? The system cleans up and consolidates unused objects
and disk storage during an IPL. If it has been longer than
usual since your last IPL, the system may require more time
to perform cleanup.
If you still think that you have a problem, make some
observations before you call software support. Watch the
codes that are displayed on the control panel. If the code
changes, that means the system has moved to another part of
the IPL. If the code does not change, write it down. This
tells what part of the IPL is in progress.
Watch the processor light on the control panel. Does it
indicate heavy activity (blinking frequently) or almost no
activity (blinking occasionally)? Write down your
observations.
Reference: F00018960
The database cross-reference (QDBSRVXR) system job maintains
the system-wide information about database cross-references,
SQL packages, and relational database directories. This
system job starts during the IPL and remains active until
the system is ended.
The file system (QFILESYS1) system job supports the
background processing of the file system. It makes sure
that changes to files are written to main storage. It also
does several general file system cleanup activities. This
system job starts during IPL and remains active until the
system is ended.
LU 6.2 Resynchronization (QLUR) system job handles the
2-phase commit resynchronization processing. This system job
is started at IPL time and remains active until the system
ends.
Reference: F00018961
Which hardcopy books are shipped with OS/400 V3R1, and do I
have to pay for them?
The following books are shipped with OS/400 at no charge.
You can order additional hardcopy books, but at your
expense:
I understand the NT-Server can run on AS/400 IPCS. If so, what file system is used?
A:
The installation process creates several server storage spaces that are used to install and run
Windows NT. AS/400 also uses these server storage spaces to load and start the Windows NT
server. AS/400 formats the drives C, D and E, as file allocation table (FAT) disks. Pre-defined
storage spaces are as follows:
What information is available to help set up Client Access/400 with TCP/IP?
A:
You can now use Client Access/400 for Windows 3.1 and Client
Access/400 Optimized for OS/2 in a TCP/IP network. For both
clients, only TCP/IP communications is provided with Client
Access/400. The versions shipped with Client Access/400 do
not include additional TCP/IP features such as Telnet or
FTP. The portion of TCP/IP that is shipped with Client
Access/400 is called the TCP/IP stack.
A special document called Installation Instructions for
V3R1M1 Windows 3.1 Client will be sent to:
This document gives detailed instructions on how to update,
migrate, or install Client Access/400 for Windows 3.1
Version 3, Release 1, Modification 1. It is recommended
that you use this document in conjunction with the Client
Access/400 for Windows 3.1 - Getting Started, SC41-3530 and
the Client Access/400 for Windows 3.1 TCP/IP Setup,
SC41-3580.
The Client Access/400 Optimized for OS/2 client supports the
IBM TCP/IP for OS/2 Version 2 stack. Client Access/400
Optimized for OS/2 ships the IBM TCP/IP stack with the
product and upgrades your current TCP/IP stack. There are
two conditions for which it will not upgrade the TCP/IP
stack:
If I have a question while installing software where do I look?
A:
The best source of information about installing OS/400
and licensed programs is to read the planning chapter in the
Software Installation book. The planning chapter identifies
basic planning steps you should consider that will prevent
or reduce errors during the installation process. Read this
before you start the installation.
Why didn't my new licensed program get installed?
A:
The automatic and manual installation procedures only
replace your currently installed level of Licensed Internal
Code, Operating System/400, and licensed programs (if they
are supported by the LICPGM menu). Appendix C of the
Software Installation book shows the licensed programs and
optional parts supported by the CLICPGM menu at the time the
V3R1M0 release initially became available.
How much memory is required when moving to Version 3 Release 1?
A:
V3R1 has some key enhancements that provide improved
performance over V2R3 such as with database, TCP/IP, APPC,
and with file serving using the FSIOP. Some areas, however,
have been identified where performance slowdowns can be
experienced. These areas are:
Several important resource intensive system jobs may still
be running after this first IPL. Support being run includes
rebuilding system catalog (database cross-reference
information) file/table and field/row information. These
jobs can use significant CPU resource and lock files and
tables during processing.
Customers may have change their IBM-supplied subsystems or
tuned their *BASE storage pool or shared storage pools.
Installation of a new release may require changes to
existing tuning parameters. After installing V3R1 and
allowing for increased machine pool storage, verify that the
pool sizes and subsystem descriptions are as expected.
What is system tuning?
A:
Tuning is a way of adjusting the performance of a system.
For basic tuning, automatic system tuning is a useful method
to maintain good performance. This can be done by setting
the system value QPFRADJ to indicate that system tuning
adjustments are to be performed at IPL time or dynamically
while the system is running.
How do I work with LAN-attached printers?
A:
When working with LAN-attached printers, you need to
understand:
How do I determine which LAN-Attached Printer Hardware I need?
A:
Several products are available from Lexmark for attaching an
ASCII printer to an AS/400 system through a LAN using
token-ring or Ethernet. They are the 4033 External Print
Server and MarkNet XLe External Print Server. Following are
the available models and a description of their functions.
4033 External Printer Server Models
Models
Communications Protocol
Type of Support
4033 001
Token Ring
Supports OS/400
4033 002
Ethernet 10BaseT
Supports OS/400
4033 003
Ethernet 10Base2
Supports OS/400
4033 011
Token Ring
Does NOT support OS/400
4033 012
Ethernet 10BaseT
Does NOT support OS/400
4033 013
Ethernet 10Base2 and 10Base5
Does NOT support OS/400 MarkNet XLe External Print Server
Note: OS/400 needs to be at V3R1 and have PTF SF21244
applied to support the MarkNet XLe device.
Models
Lexmark P/N
Communications Protocol
Type of Support
MarkNet XLe MODEL 20x
1418691
Token Ring STP/UTP
Supports OS/400 with up to 2 parallel printers
Marknet XLe MODEL 30x
1418693
Ethernet 10BaseT and 10Base2
Supports OS/400 with up to 2 parallel printers
MarkNet XLe
1418692
STP/UTP
Supports OS/400 with up to 2 parallel & 1 serial printer
Marknet XLe
1418694
Ethernet 10BaseT and 10Base2
Supports OS/400 with up to 2 parallel and 1 serial printer
How to Configure LAN-Attached Printers
The most important parameter is the source service access
point (SSAP) parameter in the line description. Following
are the values that work with the LAN print server being
used.
More detailed information can be found in the Redbook IBM
AS/400 Printing IV. GG24-4389 or the manual Printer Device
Programming, SC41-3713.
What is a PTF, and what is a cumulative PTF Package?
A:
A PTF is a temporary solution to or bypass of a problem
diagnosed by IBM as resulting from a defect in the current
release of a licensed program.
What are the benefits to migrating to Version 3 of TCP/IP?
A:
For Version 3 Release 1 Modification 0 (V3R1M0) the TCP/IP
product was restructured and repackaged. This was done with
a strong focus on upward compatibility. Therefore, IBM
provided extensive installation and conversion support to
make the migration from a pre-V3R1M0 to a V3R1M0 TCP/IP
implementation as transparent as possible. Descriptions of
each of the major items that are affected by the
restructured TCP/IP product follow:
Beginning with V3R1M0 when you purchase OS/400, the ordering
system automatically places an order for TCP/IP Connectivity
Utilities for AS/400. The V3R1M0 TCP/IP Connectivity
Utilities for AS/400 licensed program is shipped with V3R1M0
OS/400 at no additional charge!
All of the TCP/IP protocol stack; all of the configuration;
and the following TCP/IP applications were restructured for
V3R1M0: FTP, TELNET, SMTP, LPR, LPD, PING, and NETSTAT.
Additionally, FTP, SMTP, LPR, and LPD were rewritten to the
sockets API. Configuration, activation, and deactivation of
TCP/IP changed significantly. This includes removing the
QTCP subsystem and the moving of all base protocol jobs and
application server jobs to the QSYSWRK subsystem.
The 80-TCP connection limit and the 16-million-byte FTP file
and SMTP mail object size limits were removed.
New functional additions for TCP/IP provided in V3R1M0
include the following:
Performance for TCP/IP on AS/400 has improved for V3R1M0.
Most users will see this improvement through the
applications, particularly FTP, TELNET, SMTP, LPR, LPD, and
PING. The performance improvement will vary depending on
the application and network. In most environments, V3R1M0
TCP/IP and APPC performance are comparable. In general, you
should see a significant performance improvement when using
V3R1M0 compared to pre-V3R1M0 TCP/IP.
The V3R1M0 TCP/IP function was restructured by following the
TCP/IP standards, called Request for Comments (RFC), as
guides. In particular, RFC 1122 Requirements for Internet
Hosts-Communication Layers and RFC 1123. Requirements for
Internet Hosts-Application and Support were used.
The TCP/IP function has been repackaged on AS/400 business
computing systems. The base protocol stack for TCP/IP has
been moved into OS/400. This includes the TCP/IP protocol
layers of IP, TCP, UDP, and ICMP. OS/400 also contains the
SNMP agent, sockets API, PING, NETSTAT, and all of the
TCP/IP protocol stack configuration support. The TCP/IP
Connectivity Utilities/400 licensed program now contains the
major applications of FTP, TELNET, SMTP, LPR, LPD, and their
configuration support. It also contains the TCP/UDP Pascal
API.
After installing OS/400, you should install the TCP/IP
Connectivity Utilities for AS/400 licensed program.
Installation of OS/400 cleans up any pre-V3R1M0 TCP/IP
objects and commands. The conversion of the old
configuration to the new configuration automatically occurs
the first time you use a TCP/IP configuration or activation
command. A CL command is also provided to convert
pre-V3R1M0 TCP/IP CL commands in source files to their
V3R1M) syntax.
Upward compatibility is a major focus of the restructured
TCP/IP. Interoperability is maintained for all of the
applications. There are major changes for configuration
including renamed commands, changed parameters, and new
commands. Conversion routines are provided to help convert
from pre-V3R1M0 to V3R1M0 TCP/IP. The TCP/IP Pascal APl is
functionally compatible. However, programs using the Pascal
APl MUST BE RECOMPILED to run on the new protocol stack.
What should I do when my system appears hung up?
A:
First determine if your entire system is hung up or just one
job. Try to do something at another workstation. Try the
attention function.
What should I do if an IPL takes too long?
A:
If your system seems to be taking quite a bit longer than
usual to complete an IPL, start by looking for possible
reasons. Has something unusual happened that caused the
IPL, such as power outage? It is normal for the system to
take longer to start if it has ended abnormally.
What are the new system jobs at V3R1?
A:
The new system jobs for V3R1 are QDBSRVXR, QFILESYS1, and
QLUR.
What is InfoSeeker?
A:
InfoSeeker is a new function in V3R1 of OS/400 that makes
softcopy books available to non-programmable terminal users.
InfoSeeker can be thought of as BookManager® for OS/400.
IBM has BookManager readers for the OS/2, VM, MVS, DOS,
AIX®, and Windows platforms, too. With the introduction of
InfoSeeker, AS/400 users now have a wider choice of
platforms on which to choose to display softcopy.