What is INSPECT?

Inspect is an interactive symbolic debugger that enables you to isolate program bugs quickly.

Few High-Level Inspect Commands which are specific to 100 coded object files are in detail below.

IDENTIFIER
Displays information about the internal characteristics of a given data location or of all data locations in one or more scope units. The IDENTIFIER command is a synonym for the INFO IDENTIFIER command.

INFO IDENTIFIER
The INFO IDENTIFIER command displays information about the internal characteristics of a given data location or of all data locations in one or more scope units, including native symbols.

Usage Considerations

• The INFO IDENTIFIER command can be used for active and for inactive scope units in processes, PATHWAY servers, and save files. In a PATHWAY requester program, the INFO IDENTIFIER command can be used only for active scope units.
• Types of Entities - The form of the output produced by INFO IDENTIFIER for a given identifier depends on the type of entity the identifier denotes.
• INFO IDENTIFIER Presentation for Variables - A typical program contains more identifiers for variables than for any other entity class.

MATCH
The MATCH command searches for scope-unit names or other identifiers in the current program.

Default Values

• If the MATCH IDENTIFIER command is entered with only one pattern, Inspect will display only the matching symbols, and the scopes they were found in.
• If the VERBOSE clause is omitted, scope names are displayed only if they have a matching pattern.

Usage Considerations

• Matching Uppercase and Lowercase Letters - The MATCH command does not distinguish between uppercase and lowercase letters in the pattern unless the current language is C.
• Alias Restrictions with the MATCH command - Aliases are not be expanded in the pattern with the MATCH IDENTIFIER or the MATCH SCOPE commands.
• Matching Scopes With a Leading “#” - You must include a “#” to match scopes which have a leading “#”. For example, to match the scope, “#global”, enter: MATCH SCOPE ##global

Impacts and Top Recommendations for HP Integrity NonStop Users

Different Object File and Native Processor Types

Object File Code	Object Type	Native Processor Types
100	TNS	CISC (Complete Instruction Set Computing) for the Tandem Processor. - TNS objects (COBOL, TAL, etc) will be interpreted on Integrity Platforms
700	TNS/R	RISC(Reduced Instruction Set Computing) for the MIPS Processor - TNS/R Native object files cannot be executed on a TNS/E Platform. All TNS/R  Native Programs must be recompiled using a TNS/E Native Compiler(for Native 800 Object) OR the TNS Compiler(for interpreted 100 Object)
800	TNS/E	EPIC(Explicitly Parallel Instruction Computing) for the Intel Itanium Processor - TNS/E Native Object Files cannot be executed on a TNS/R Platform. - OSS Programs must be migrated to TNS/E Platform - All TNS/E Native Code is position independent code (PIC)

Corporates today depend on HP Integrity NonStop mission-critical servers

Modern HP Integrity NonStop Servers continue to deliver on hallmark attributes -
   - Availability,
  - Scalability and
  - Data Integrity

The HP NonStop Server continues to be the industry leader in mission-critical availability and reliability, with an extensive footprint in financial services and telecommunications marketplaces, and the customers who deploy NonStop have been spared the ignominy that can come with unwanted media coverage.

Few recent wins.

- In America, PULSE selects four NB54000c for Credit Scoring

- In India, Mobile phone operator depends on 300 NonStop processors

- In Norway, Healthcare is operating with NonStop

- In Singapore, Shippers move containers NonStop

- In Germany, auto manufacturer never unseated

HP NSS Vs HP NSB(Blade Servers)

For Migration from COBOL to Java - POC Details

HP and Blu Age® completed a multi-step migration and modernization Proof of Concept (POC) project that took a legacy OLTP application from COBOL and DB2 on an IBM mainframe,

 - First to Java and DB2 on the HP ProLiant DL360 platform, &

 - Ultimately to Java and SQL/MX on an HP NonStop Server.

The project included comparisons of transaction execution times in the

    - ProLiant environment,

    - a hybrid NonStop and

    - Windows environment, and

    - a “pure NonStop” environment.

The NonStop Server was clearly the overall winner for the set of transactions comprising this POC.

The Blu Age1 software suite implements

- Model Driven Architecture (MDA) principles &

- Offers appropriate methods to deliver Service Oriented Architecture (SOA) application programs written in Java.

The Reverse Modeling component facilitates the extraction of business logic from the legacy code and constructs UML (Unified Modeling Language) models that can be used to generate the application in a Java framework.

The Blu Age software is packaged as a plugin for Eclipse, an open source IDE (integrated development environment) frequently used to develop Java applications.

POC configuration

Configuring the hardware and software for this POC required no extraordinary efforts.

Standard 1 GB Ethernet connections were used to connect these hardware components used for testing:

• NonStop Server: NS16004, with 10 mirrored data drives, running H06.25, SQL/MX 3.2, and NonStop Java 6.0 (1.6).

• Windows server (for Java middle layer): HP ProLiant DL360 G5, running Windows Server 2008, Java 1.6 and Blu Age 3.7.

The middleware setup required installing JBoss 7.1.1 and its dependencies.

A few minor (and common) DDL adjustments were made when the NonStop SQL/MX tables were created:

- VARCHAR columns with lengths less than 20 were changed to fixed CHAR columns of the same length. (This is a typical optimization practice for NonStop SQL.)

- BIGINT columns were changed to the equivalent NonStop SQL/MX data type, LARGEINT.

- Columns declared with DEFAULT NOT NULL syntax were given a default value of 0.

Availablity , Statistics and Performance (ASAP)

ASAP Monitors hundreds of Objects in Real-Time.

It Provides goals and actions to repair or restart system and Application Components.

ASAP has a wide range of visual and programmatic interfaces,
       - Including EMS,
       - Conversational interface,
       - Fat and thin client interfaces,
       - Provider/Consumer APIs
       - Email
       - Phone Notifications with color-coded HTML reports
       - Customizable GUIs with user-defined Dashboards and
Long term Historical Database with up to eve 10 years worth History of all Availablity,
statistics and performance data.

ASAP Can integrate with HP operations manager.

ASAPX in an API into the ASAP infrastructure to monitor the availablity and performance ob abstract application domains.

ASAP Hybrid plug-in for Linux integrates Linux Application metrics into ASAP, providing a visa of the entire application spanning across Nonstop and Linux systems.
       

Checklist - To migrate into OSS - VI - And Thats it :)

After System and Database updates, Next step would be Application Installation.

ID	Task Description	Prior Task	Resource	Remarks
24	Place Application in Dir. Structure	11,19	Applications	Expand the Application Delivery Package and Place into the proper delivery structure. This often requires utilities like TAR,GZIP and/or Jar.
25	Configure Pathway and Serverclass	24	Applications	Configure Pathmon/Pathway Naming, Locations and server classes(including environment variables) - If needed
26	Deploy .war files for web interfaces	25	WebAdmin	Deploy distributed .war files
27	Configure Externalized properties for web interface(s)	26	WebAdmin	Modify Externalized properties for IP addresses, catalogs, schemas and user-id.

ID	Task Description	Prior Task	Resource	Remarks
28	Configure Online Dumps	21	Database, Systems, Operations	Use TMFCOM to configure online dump schedules for database protection
29	Configure Scheduled Backups	27	Database, Application, Operations, Systems	Determine backup fileset, schedule and methods; Implement in batch scheduler.(Each OSS pathname has a corresponding Guardian Filename)
30	Identify Logs to Monitor	27	Database, Applications, Operations, Systems, Interface Group, WebAdmin	Identify Logs to Monitored across the enterprise. Ported Applications will NOT typically use VHS or EMS.

Checklist - To Migrate into OSS - V

When the System is READY, the next steps is for DBA Team to prepare and execute DDL Scripts and prepare database for use.

ID	Task Description	Prior Task	Resource	Remarks
20	Modify DB scripts for Disk Layout	3	Database	Edit SQL DDL Scripts to distribute the database.
21	Create the Application Schemas and Tables	20.21	Database	Obey the scripts in MXCI to create the Application schemas and Tables
22	Create MetaData (catalog) convenience views{optional}	21	Database	Download and run in OSS the mxschema utility to create views of database metadata tables
23	Create datasource for J/ODBC access	18,21	Database	Use mxcs or NSM/Web to create a data source.

Checklist - To Migrate into OSS - IV

ID	Task Description	Prior Task	Resource	Remarks
16	Create Resolver Links for TCP/IP	15	Systems	Edit, In Guardian Space, $system.ZTCPIPHOSTS & RESCONF, In OSS, create symbolic links for HOSTS, RESOLV.CONF, PROTOCOLS, NETWORK and SErvices in the /etc directory
17	Create Data service	16	Systems	Use SCF to add a Data Service
18	Add "DBA.manager" to MXCS	17	Systems	Use MXCS mode of MXCI to grant OPERATOR privileges to the dba.manager user.
19	Install any open source utilities	18	Systems	Identify the useful utilities and install those. Modify the /etc/profile and users .profile files.

Checklist - To Migrate into OSS - III

ID	Task Description	Prior Task	Resource	Remarks
11	Create Application Directories	10	Systems	Establish OSS directory for Application like APPL, BIN etc
12	Install SQLMX	11	Systems
13	Install Java	12	Systems
14	Install Java-addons and other software required for Application	13	System	Following Components needed - J/ODBC drivers - JToolKit- Contains APIs - Javaservlets - Required for WebApps - HP Jmeter for Nonstop Java - Performance Anlayse Tool
15	Initialize JDBC	14	Systems

Checklist - To Migrate into OSS - Part II

ID	Task Description	Prior Task	Resource	Remarks
6	Move QIO to KSEG2 (Required for Java)	3	Systems	Use SCF to move QIO to KSEG2. And Reboot.
7	Configure TMF	6	Systems	Use TMF to configure TMF components and Objects: Audit Trails, Dump and restore volumes etc
8	Create Mount Point Dir	8	Systems	Use OSS to establish mount point directory
9	Create Disk Pool	9	System	Create Disk pool Definition Files / Scripts
10	Start the Filesets	10	Systems	Use SCF to add and start a name server If needed. Then, add and start a fileset for the new mount point.

Checklist - To Migrate into OSS - Part I

Tokenization : Creating Secure Test Data

PCI DSS Section 6.4.3 requires that "Production Data (live PANs) are NOT used for Testing or Development".

If we need a Huge Dataset of real looking PANs for a Test. How do we create those?

A good Tokenization will allow you to do "BATCH COPY" where you start with PAN Data and end up with Tokens.

Doing this in production once is a fast and secure way to create test data: when configured properly, the tokens can look like "REAL" PANs and can even pass Luhn check.

Thus creating a huge set of Test data which is NOT tied to real PAN data at all becomes easy exercise.

Challenges of being a Tandem DBA

• Repartition
• Reviewing and updating key values
• Merging Partitions
• Reuse Partitions
• Update statistics
• Gathering SQL/MX statistics
• Copy Statistics from One Table (or system) to Another
• Index maintenance
• Create
• Populate
• Drop
• Alter
• Specifying Access Previleges
• Grant
• Revoke
• Query Performance Tuning
• Building and Deploying Standard Queries
• Dataload/Unload
• Moving Data from MP to MX for Testing