26.10.2014 Views

z/VSE: 45 Years of Progress - z/VM - IBM

z/VSE: 45 Years of Progress - z/VM - IBM

z/VSE: 45 Years of Progress - z/VM - IBM

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

the<br />

Challenge<br />

managing<br />

<strong>of</strong><br />

Large<br />

complex<br />

Environments<br />

By Stephen Mitchell<br />

Modern, highly scaled CICS<br />

applications can make use<br />

<strong>of</strong> resources across many<br />

individual CICS regions<br />

running on multiple Logical<br />

Partitions (LPARs) even in different time<br />

zones. Real-time monitoring <strong>of</strong> such<br />

infrastructures has become suboptimal,<br />

given the way they’re now used. Service<br />

outages can have a devastating impact<br />

on business and must be minimized.<br />

CICS systems programmers and<br />

other support personnel at large CICS<br />

sites become concerned when asked to<br />

investigate operational issues if they’re<br />

only given the name <strong>of</strong> the CICS application<br />

that needs attention. The problem<br />

is this doesn’t pinpoint the<br />

infrastructure involved.<br />

Consider, for example, an application<br />

initiated via one <strong>of</strong> several instances <strong>of</strong><br />

CICS Transaction Gateway (CTG) executing<br />

on several different z/OS LPARs.<br />

The CICS transactions involved could<br />

be started in any one <strong>of</strong> many CICS<br />

regions where the application code executes<br />

and is sent to CICS over Logical<br />

Unit 6.2 (LU6.2) connections. These<br />

could call on programs or resources in<br />

other specific and connected CICS<br />

regions or from one <strong>of</strong> a group <strong>of</strong> CICS<br />

regions. The resources used could<br />

include DB2 data, in which case the DB2<br />

connection and suitably configured DB2<br />

entries and DB2 transaction resources<br />

may be needed in those regions. The<br />

application programs may access VSAM<br />

files, either locally in the same CICS<br />

region or remotely in a File Owning<br />

Region (FOR); perhaps special CICS<br />

Temporary Storage Queues (TSQs) are<br />

used. Maybe when the application has a<br />

problem, it habitually abends with a certain<br />

known transaction abend code; if<br />

the application uses the services <strong>of</strong><br />

WebSphere MQ, then the MQConnection<br />

needs to be active in the CICS region or<br />

regions. Figure 1 shows the basic CICS<br />

infrastructure that might be involved in<br />

such an application.<br />

It’s also <strong>of</strong>ten true that an accurate,<br />

timely diagram or document describing<br />

the CICS resources an application uses<br />

isn’t readily available when it’s most<br />

needed. Even if this information is available,<br />

the traditional CICS monitors can<br />

only show a small subset <strong>of</strong> the CICS<br />

infrastructure to the support analyst at<br />

one time.<br />

Considerable time can elapse while<br />

support personnel try to understand<br />

just what should be inspected; this is<br />

frustrating for all involved. Serviceimpacting<br />

incidents aren’t resolved as<br />

z / J o u r n a l • O c t o b e r / N o v e m b e r 2 0 1 0 • 5 5

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

Saved successfully!

Ooh no, something went wrong!