29.06.2013 Views

NATURAL PROCESS Extends NATURAL to Operations Center

NATURAL PROCESS Extends NATURAL to Operations Center

NATURAL PROCESS Extends NATURAL to Operations Center

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

. <strong>NATURAL</strong> 2:<br />

- .<br />

.- . SM03 S<strong>to</strong>rage Control<br />

'-- -<br />

Chris Yandall<br />

<strong>NATURAL</strong> Systems Support Specialist<br />

Cus<strong>to</strong>mer Service Division<br />

When Software AG's Jon Church<br />

. . - started <strong>to</strong>ying with the idea of<br />

-<br />

stealing the task of s<strong>to</strong>rage manage-<br />

- ment away from CICS and began<br />

dreaming up the now grandparent<br />

components of the current<br />

,<br />

I<br />

<strong>NATURAL</strong> 2 S<strong>to</strong>rage Control System,<br />

he envisioned a day when<br />

<strong>NATURAL</strong> would celebrate performance<br />

benefits unparalleled by any<br />

other complex 4th generation software<br />

<strong>to</strong>ol.<br />

Well, that day has come. It <strong>to</strong>ok<br />

, .<br />

k ' . some doing <strong>to</strong> get users <strong>to</strong> uncover<br />

k '<br />

5- the myriad of bugs awaiting <strong>to</strong> chew<br />

F -<br />

I.. through the terminal screens and<br />

.-- manifest themselves in the form of<br />

abundant incident reports (logs),<br />

but it appears the worst is over.<br />

With the help of Software AG<br />

United Kingdom, Ltd.'s Mike Meehan.<br />

the current author and new<br />

<strong>to</strong>rch bearer for the S<strong>to</strong>raae Control I<br />

System, <strong>NATURAL</strong> is now outperforming<br />

its great-granddaddy,<br />

<strong>NATURAL</strong> V1.2, in whopping<br />

strides. Most of the blatant software<br />

slip-ups have been mopped up<br />

and now the true <strong>NATURAL</strong> nucleus<br />

is surfacing <strong>to</strong> shine as a new<br />

dimension in software solutionsthanks<br />

<strong>to</strong> Mike's genius and<br />

determination.<br />

. .<br />

Included in SM03 .~ :-.<br />

Here are a few of the major en-<br />

hancements and features included<br />

with Mike's new System Mainte-<br />

nance 03 (SM03):<br />

By popular demand, the ability<br />

<strong>to</strong> share Threads and Roll files<br />

across multiple <strong>NATURAL</strong> nuclei<br />

under one CICS session or with<br />

MRO has been res<strong>to</strong>red as in<br />

SMO1. Therefore, the System<br />

Control Block is now a separate<br />

entity and will require its own<br />

PPT entry. With this res<strong>to</strong>ration,<br />

multiple nuclei may be added<br />

without concern of reinstallation<br />

of Threads and Roll files. Con-<br />

cern only is warranted when<br />

new systems demand more re-<br />

sources due <strong>to</strong> a sizable increase<br />

in system activity.<br />

1 The Thread allocation/selection<br />

t<br />

algorithm has been improved<br />

since SM02. With SM03, a user<br />

count field has been added per<br />

thread, which will reduce the<br />

number of physical roll-ins from<br />

disk.<br />

The Thread contents are now<br />

compressed before rollout, re-<br />

ducing disk 110 for roll out and<br />

roll in (fewer records written and<br />

read). European sites which are<br />

beta testing SM03 have seen a<br />

50% reduction in I10 during<br />

their initial testing. The<br />

<strong>NATURAL</strong> nucleus is also per-<br />

forming compression on data<br />

streams internally, which will<br />

allow even more performance<br />

savings.<br />

SM03 includes a facility that<br />

detects NEWCOPIES for the<br />

<strong>NATURAL</strong> nucleus, which in the<br />

past usuallv resulted in a<br />

~ ~ ~ 0 6 0 2<br />

CICS session abend. Therefore,<br />

user sessions managed by the<br />

AMIBSQL: .<br />

or some other fatal CICS.<br />

I<br />

old copy would be detected and<br />

terminated. This must be done<br />

because the Roll Files are reset<br />

whenever the System Control<br />

Block is refreshed. So, whenever<br />

<strong>NATURAL</strong> is NEWCOPIED, the<br />

current sessions will be termi-<br />

nated <strong>to</strong> avoid conflicting usage<br />

of the active RESIDENT PPT.<br />

All in all, the best is yet <strong>to</strong> come. 1<br />

Development on S<strong>to</strong>rage Control is<br />

a never-ending battle <strong>to</strong> ensure all I<br />

code becomes bulletproof. There<br />

is even talk of a <strong>NATURAL</strong> that<br />

will never bring down CICS-no<br />

matter how poorly an application is<br />

coded.<br />

For now, let's just be pleased that<br />

we have a viable structure that can<br />

be built on for the future genera-<br />

tions of auplications and releases cf -<br />

A A<br />

.<br />

Converting ADAMINT. <strong>to</strong> :.<br />

1 ADABAS SQL<br />

Ken Marcum<br />

I ADABAS Product Support Representative<br />

Cus<strong>to</strong>mer Service Division<br />

With all of the talk and planning<br />

regarding ADABAS 5, many of you<br />

may be wondering-even fearing-<br />

about the future of applications<br />

using ADAMINT. Well, wonder and<br />

fear no more. AMI2SQL will allow<br />

users of ADAMINT <strong>to</strong> migrate eas-<br />

ily <strong>to</strong> ADABAS SQL with minimal<br />

conversion effort and expense.<br />

With ADABAS SQL, the new func-<br />

tionality in ADABAS 5 may be uti-<br />

lized by the applications<br />

programmer. ADAMINT will exe-<br />

cute under ADABAS 5, as it does<br />

with ADABAS Version 4; however,<br />

ADAMINT will not be enhanced <strong>to</strong><br />

incorporate any new features found<br />

in ADABAS 5. After converting<br />

the existing ADAMINTs using<br />

AMI2SQL, the power of<br />

ADABAS 5, PREDICT, and SQL<br />

will be realized.<br />

How does AMI2SQL work? It reads<br />

an entire ADAMINT source parti-<br />

tioned data set (PDS) and creates - -<br />

ADABAS SQL statemeats for each<br />

member within the ADAMINT<br />

PDS. The generated COBOL/<br />

ADABAS SQL programs are then<br />

preprocessed through ADABAS<br />

SQL, compiled, and link-edited.<br />

The new COBOLIADABAS SQL .<br />

subprogram(s) may then be dynam-<br />

ically loaded or statically link-ed-<br />

ited <strong>to</strong> the user program in the<br />

same manner as ADAMINT.<br />

AMI2SQL does not modify the use<br />

program in any way. Rather,<br />

AMIZSQL simply replaces the I<br />

ADAMINT subprogram with a -<br />

COBOL subprogram with embedded<br />

ADABAS SQL statements.<br />

After conversion, this source is .<br />

fully maintainable by an application<br />

programmer.<br />

-.<br />

AMI2SQL converts nearly 100% of<br />

all ADAMINT source modules. The<br />

following considerations may necessitate<br />

user application program<br />

or ADAMINT source modification:<br />

A maximum of 2,000 members<br />

I<br />

l<br />

COBOL programs with embedded -<br />

<strong>to</strong> be translated may exist in the<br />

- ADAMINT PDS.<br />

-<br />

continued on page 14<br />

5<br />

7<br />

-.<br />

I<br />

I

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!