Software AG's New Headquarters - the Information Technology ...
Software AG's New Headquarters - the Information Technology ...
Software AG's New Headquarters - the Information Technology ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
SOUTHWESTERN REGION<br />
John Farmer<br />
Discusses<br />
Installation and<br />
Internals<br />
Laurie Hanley<br />
TGI Friday's, Inc.<br />
The August 5th Southwest Region<br />
Users' Group meeting was called to<br />
order by Kerrie Meyler, <strong>the</strong> Southwest<br />
Regional Representative. The<br />
following orders of business were<br />
covered:<br />
1. General Business<br />
2. ADABAS 5 by John Farmer,<br />
<strong>Software</strong> AG<br />
3. PREDICT V2.3 discussion by<br />
Randy Kastendick, <strong>Software</strong> AG<br />
4. NATURAL 2 DESIGN discussion<br />
by John Wheat, University of<br />
Texas at Austin<br />
5. Round Tablelopen Forum<br />
General Business<br />
Several persons have asked how to<br />
receive <strong>the</strong> minutes and agenda<br />
from <strong>the</strong> Regional meetings. All<br />
minutes and meeting information<br />
are distributed through <strong>the</strong> Regional<br />
office. If you are not receiving<br />
this information, you should<br />
contact your Regional office: specifically<br />
Jon Hoaldridge in Dallas or<br />
Doug Roberts in Houston. In many<br />
cases only one copy of <strong>the</strong> information<br />
is sent to each user site. Often<br />
this may be sent to <strong>the</strong> wrong person<br />
who is not forwarding <strong>the</strong> information<br />
or distributing to <strong>the</strong><br />
proper personnel. If you are not receiving<br />
<strong>the</strong> information, you should<br />
contact Jon or Doug and confirm<br />
your distribution information.<br />
If you wish to obtain a copy of <strong>the</strong><br />
minutes from o<strong>the</strong>r Regions, you<br />
may contact John Oborn, <strong>the</strong> new<br />
Regional Representative.<br />
There is a new newsletter titled<br />
VVAN (VAX-VMS-ADABAS-<br />
NATURAL) which is being distributed<br />
among <strong>the</strong> DECIVAX users. If<br />
you have not received a copy of this<br />
newsletter and are interested in<br />
being on <strong>the</strong> mailing list please<br />
contact Kerrie Meyler or John<br />
Oborn.<br />
Elections for Southwest Region officers<br />
were held at this meeting!<br />
The new elected officers are:<br />
PresidentlRegional Rep.<br />
John Oborn<br />
Vice PresidentlPgm Coord.<br />
John Baird<br />
ADABAS 5<br />
John Farmer, <strong>Software</strong> AG, discussed<br />
ADABAS 5 installation and<br />
internals. He brought forward several<br />
very important points to note:<br />
The ADABAS 5 Internals Manual<br />
can only be obtained by attending<br />
<strong>the</strong> <strong>Software</strong> AG Internals<br />
course.<br />
You can convert from V4 to V5<br />
without unloading files.<br />
When installing ADABAS 5, you<br />
may perform a temporary or a<br />
permanent install of <strong>the</strong> SVC.<br />
When installing a temporary SVC<br />
you are not required to IPL.<br />
NOTE: The temporary SVC install<br />
is not possible for DOSIVSE<br />
users.<br />
AMODEIRMODE parameters are<br />
only required for MVSlXA shops.<br />
ADARUN is not upward compatible;<br />
you must have a V5<br />
ADARUN module to execute<br />
ADABAS 5.<br />
ADALNK is upward compatible;<br />
<strong>the</strong> TP links are NOT.<br />
ADASIP <strong>the</strong> (SVC Install Program)<br />
must be executed after<br />
each system IPL.<br />
ADASVC is loaded into and executed<br />
within <strong>the</strong> CSA.<br />
You cannot use 1'4 PLOG files<br />
with V5 nucleus; <strong>the</strong> checkpoint<br />
files are different.<br />
The BLKSIZE is larger on V5 for<br />
3380 devices; you must change<br />
your WORK dataset.<br />
You should alter <strong>the</strong> GCB entry<br />
for <strong>the</strong> number of blocks on <strong>the</strong><br />
WORK dataset before <strong>the</strong> V5 nucleus<br />
is initiated. This is discussed<br />
in both <strong>the</strong> Implementation<br />
Manual and <strong>the</strong> Users Guide.<br />
Also, when ADAWS NEW-<br />
WORK is run to alter <strong>the</strong> WORK<br />
dataset size in <strong>the</strong> GCB it only alters<br />
<strong>the</strong> GCB it does not alter <strong>the</strong><br />
actual size of <strong>the</strong> WORK dataset.<br />
Any user exits will have to be<br />
modified for V5.<br />
If you revert back to V4 from V5,<br />
you must first remove any<br />
HYPER Descriptors.<br />
The ADABAS 5 nucleus has been<br />
modified so that no user may<br />
take up more than 25% of <strong>the</strong><br />
hold queue; if a user attempts to<br />
place a number of records in <strong>the</strong><br />
queue larger than <strong>the</strong> maximum<br />
number of records setting, <strong>the</strong>y<br />
will receive a non-zero response<br />
code.<br />
The ADARUN parameter PLOG<br />
RQ=NO is <strong>the</strong> default parameter<br />
for <strong>the</strong> PLOG. This specifies that<br />
<strong>the</strong> MPM will come up with a<br />
PLOG as <strong>the</strong> default.<br />
The ADARUN parameter<br />
"UTIONLY" specifies that <strong>the</strong><br />
nucleus is brought up only in<br />
utility mode, users may not log<br />
on. The "UTIONLY =NO"<br />
parameter will return <strong>the</strong> MPM to<br />
use by users.<br />
ADABAS 5 will reformat a part of<br />
a RABN.<br />
When you delete a file in<br />
ADABAS 5, you may keep <strong>the</strong><br />
FDT entry. When you reload <strong>the</strong><br />
file, you may point to <strong>the</strong> FDT<br />
entry and specify <strong>the</strong> cards<br />
without having to recreate <strong>the</strong>m.<br />
You may now set a minimum ISN<br />
# to save address converter<br />
space.<br />
The DSTAT operator console<br />
command will display <strong>the</strong><br />
activity of a utility.<br />
Several processing statistics such<br />
as <strong>the</strong> number of blocks used on<br />
a SORT, etc. will be printed along<br />
with <strong>the</strong> ADALOD utility output.<br />
If you receive an error 10 when<br />
running a utility, it will tell you<br />
what DIB entry was in conflict.<br />
The ADASAV drive parameter<br />
can use up to 8 tape drives at one<br />
time. This will allow parallel<br />
activity to multiple drives to<br />
speed up backup and restore<br />
times.<br />
With ADARES BACKOUT, in V4,<br />
when it got to <strong>the</strong> end of tape 1 it<br />
would back out <strong>the</strong> end if you<br />
were not at ET status. Thus you<br />
could loose <strong>the</strong> end of one tape<br />
and <strong>the</strong> beginning of <strong>the</strong> next. In<br />
V5 you may specify no backout<br />
to prevent this from happening.