AS400 Iseries

IBM System i APIs at Work

2011-05-14T08:44:00.005+01:00

IBM System i APIs at Work

Click to Read Reviews and look inside book on Amazon

Product Details
Paperback: 550 pages
Publisher: Mc Press; 2nd edition (September 1, 2007)
Language: English
ISBN-10: 1583470697
ISBN-13: 978-1583470695
Product Dimensions: 8.8 x 7 x 1.4 inches
Shipping Weight: 1.8 pounds
Average Customer Review: 5.0 out of 5 stars
Amazon Bestsellers Rank: #1,211,750 in Books

APIs are OS provided tools that allow us to extend our ability to solve business problems on the system i. Most System i developers do not have a good understanding of the available APIs or their workings within i5/OS so are not able to get the best out of them.

IBM API expert author Bruce Vining guide us to mastering the wide APIs available with System i i5/os with real examples that can be applied in your environment.

Developers these days have to integrate applications running on various operating systems and languages to implement business rules and requirements. APIs allow you to solve some of the harder to crack implementation issues by giving you access to the lower level structures of the os or application, making these some of the most useful tools in your arsenal.

• New chapters covering topics such as exit point concepts, Integrated File System, date and time, cryptographic services, TCP/IP, and more
• Sorting, character data conversion, and user application information
• APIs are covered in depth
• Fully updated code on previous APIs to bring them up to newer standards
• Updates to API changes since the previous edition
• Modernized RPG code to demonstrate current coding style
• An Appendix with COBOL examples and implementation including API equivalents for RPG support of memory management, bit testing, edit words, and more
• Check Your Knowledge tasks at the conclusion of each chapter with solutions provided in RPG and COBOL Write client and server applications that enable your System i to communicate with other systems, such as PCs, using sockets

What Jon Paris said about this book

It is difficult to imagine a more comprehensive guide to APIs than that contained within these covers. From list APIs, to Telnet, to encryption, Bruce covers them all and does so in an informative and entertaining fashion. Not content simply to detail their naked operation, Bruce also demonstrates the usage of these APIs as the foundations for a number of utility programs that most shops will soon spot a use for in their daily operations. Even better - the examples are terrific demonstrations of the power of the RPG IV language. If you were to purchase this book for no other reason than to study the examples you would get excellent value for money. Hopefully some of the folks involved in producing IBM documentation will read this book and take the hint! COBOL users are not left out either - Bruce provides COBOL versions of all of the code.

At well over 700 pages this is indeed a weighty tome, but unlike so many others there's no "fat" here - just solid content that will satisfy your hunger for knowledge

What Is Lansa

IBM System i APIs at Work

What is LANSA

2010-04-02T01:10:00.004+01:00

What is LANSA

LANSA's integrated software suite, from LANSA

LANSA’s software suite contains four flagship products, and a set of ancillary products, that can be deployed individually to solve specific requirements or woven into an entire infrastructure. Think of each product as a building block that is not only optimized for a specific task but that is also a big step forward in deploying a new platform.

The only IDE you will ever need for Windows or System i

Visual LANSA is the name of our Integrated Development Environment (IDE) for building, modernizing and integrating business applications. Visual LANSA has followed a twenty-year product evolution path that has proven its superiority over other application development tools and methodologies. Today Visual LANSA is used by thousands of developers, spread across different industries and countries around the world, who are all in pursuit of the same objective: maximum productivity and simplicity throughout the entire software development life cycle.

The fastest and most certain way to modernize your System i applications

RAMP is a complete process for rapidly modernizing legacy software systems. Before the advent of RAMP, users of System i, iSeries or AS/400 servers facing application modernization challenges were forced to either throw it all away and start again or continue to build upon, and be limited by, their legacy 5250 business systems. Now RAMP offers the perfect balance between those two extremes. By providing an application development framework that combines functionality from green-screen applications with new visual components in a rich graphical user interface, RAMP addresses your immediate tactical needs and sets you on a path of evolution without limits.

Flexible integration of business processes, systems, applications and data

LANSA Integrator, is a versatile and extensible integration server that is used by programmers to exchange data in any format or via any protocol and can also be used to remotely call functions in other systems. LANSA Integrator enables integration of Application-to-Application (A2A) and Business-to-Business (B2B) transactions through XML and Java services. LANSA Integrator allows bi-directional XML – and other data formats – to be exchanged between you and your trading partners, regardless of platform. LANSA Integrator appeals to developers with LANSA, RPG, COBOL or Java skills and is regarded as the Swiss army knife of the integration world.

LANSA Composer is a Business Process Integration (BPI) tool that gives business analysts a top-down view of end-to-end business processes. LANSA Composer provides connectivity between different systems in the same way as LANSA Integrator, but differs by including a graphical mapping tool and a process orchestration engine. These additions make LANSA Composer a highly visual and code-free tool that any business analyst or expert user can operate. The purpose of a BPI tool like LANSA Composer is to automate manual processes and eliminate rekeying of data by reducing the amount of paper, email, fax and human interaction required to complete a given business process.

ERP extensions, middleware, reporting and eCommerce

Alongside these flagship offerings, LANSA has products in areas ancillary to the main LANSA platform like end-user reporting (LANSA Client) and middleware (LANSA Open for .NET). We have also created specific application products where we saw a market need for an out-of-the-box solution e.g. an open-source ERP package, an eCommerce store, an EDI gateway, an AS2 compliant secure communications server and a Product Information Management (PIM) solution for on-boarding to the Global Data Synchronization Network (GDSN).

LANSA your one-stop shop

What is RPG Smart Pages

The theme running throughout our suite is that all products are built on, and share the underlying services, of the LANSA platform. We, along with our vibrant business partner community, have broadened our value proposition beyond tools and technology into application solutions so that LANSA can be your one-stop-shop

What is RPGsp (RPG Smart Pages)

2010-04-02T01:02:00.001+01:00

What is RPGsp (RPG Smart Pages)

RPGsp is an award-winning rapid Web development environment that has been proven and trusted by thousands of System i users. Whether you need to extend your existing legacy programs or build new applications, RPGsp can deliver phenomenal results in a short amount of time.

With RPGsp, you will save time by using existing RPG resources and not having to rewrite code or retrain your staff. You will increase your productivity with the help of cutting edge tools like intuitive point-and-click wizards, HTML design, visual debugging, advanced RPG editing, code analysis, and hybrid compiling. You will instantly construct advanced applications like dynamic graphs, inquiries, drill-downs, BI dashboards, and file maintenances. RPGsp supports the latest in SOA, Web Services, AJAX, Web 2.0, and eCommerce to help you build the most interactive and flexible applications.

Native System i Web Development
Web applications are business applications. Why not then use RPG, the platform's undisputed best business language, to build modern IBM i Web applications? RPGsp (RPG Smart Pages) enhances the native RPG language to have powerful Web capabilities. This makes it a true Web development language, with all of the features a modern Web language should have, including AJAX, SOA, Dynamic HTML, Forms, Cookies, and much more. System i developers feel right at home in this environment. Finally, you can get to the Web without middleware, third party application servers, or Websphere.
^ Back to top ^

Short Learning Curve
Build on what you already know. If you are already familiar with standard RPG, you can start building Web applications right away. Even non-programmers can create applications in minutes by using any of the powerful wizards that are available. You will have access to comprehensive documentation, numerous examples, and detailed HTML/RPG references to help as you begin coding your applications.
^ Back to top ^

Rapid Development
With RPGsp, application development is now faster than ever before. You can build all kinds of applications within minutes. Choose from an abundance of rapid application development tools to speed development tasks. Instantly build advanced dynamic fields like data-driven dropdowns and list boxes. Reuse any of your existing code, including RPG, CL , DDS, and HTML. Control all HTML attributes in a point and click manner, and let our comprehensive designer write most of the HTML for you. Plus, you can quickly build applications such as advanced database inquiries, file maintenances, drill-downs, header/detail screens, pop-up selection windows, data entry forms, and much more without manual coding.
^ Back to top ^

Numerous Wizards, Templates, and Snippets
New to Web development? Our IDE is packed with wizards and templates to get you going. Just pick a template and RPGsp will walk you through creating the application. You can quickly create working programs without writing any code. You will end up with clean ILE RPG code (free or fixed format) working together with dynamic HTML output. As you maintain your application, you will have access to various code snippets for RPG, CSS, and JavaScript. Also included is a ready-made AJAX library which allows you to easily integrate Web 2.0 features, exchange XML, or use Web services.
^ Back to top ^

Built-in Charting
Creating interactive charts, dashboards, and KPI's with RPGsp is as simple as point and click. Just follow our comprehensive step-by-step wizards to build any type of single-series, multi-series, or combination chart. Our wizards offer hundreds of options to help you build comprehensive applications for visualizing your business data. Pick from 2D or 3D Column Charts, Bar Charts, Line Charts, Area Charts, Pie Charts, Doughnut Charts, and more. Each type of chart is completely customizable with data being built either by record level RPG code or SQL. You can easily make the charts interact with each other or with other Web components. Users may click on the chart to drill-down and/or activate another chart.
^ Back to top ^

Intelligent Code Editing and Design Tools
RPGsp comes with an award winning code editor. It is full of helpful features such as HTML reformatting, fixed to free format conversion, intelligent prompting, code outlines, syntax highlighting, and context-sensitive help. It supports both Web and back-end languages, including JavaScript, CSS, HTML, RPG, CL, and DDS. In addition, you can visually inspect your application with our built-in HTML designer. The designer can automatically render dynamic RPG and resources residing on the System i. It may also be launched in Split-View, which allows developers to work with Code and Design at the same time in one view.
^ Back to top ^

Integrated Visual Debugger
RPGsp offers 3 different ways to debug RPG-based web applications, including a completely integrated Visual Debugger. The Visual Debugger provides unique features such as variable evaluation on hover, job-transparent debugging, and even the ability to step back in time to examine execution history. You will be able to set breakpoints and visually step through running Web applications while reviewing both RPG and HTML code in one view.
^ Back to top ^

Cross-platform Capabilities
RPGsp pages can read or update Oracle, SQL Server, MySQL, MS Access, and other databases. Created programs will be able to communicate with other Web applications running on any platform. Your applications will also have complete support for SOA, XML, AJAX, and Web services.
^ Back to top ^

Unmatched Performance
RPGsp produces lightening fast CGI code. Our unique "look-ahead" compile technology allows for performance up to four times faster than other native technologies, such as CGIDEV2. Your applications will run entirely in batch processing.
^ Back to top ^

Rock Solid Security
RPGsp applications reside entirely on the System i and take full advantage of the system's object-based architecture to protect against viruses, malicious scripts, hackers, and other threats. You also receive another layer of security by having your Web applications separated from the rest of the system. Complete support for SSL is provided.
^ Back to top ^

Automated Server Configuration
Install the development environment and configure the Web server in less than five minutes using RPGsp's intelligent server analysis and configuration utilities. Effortlessly configure logging and user authentication with easy to use wizards.
^ Back to top ^

Automatic Conversions
Move your existing applications to the Web rapidly. No more screen-scrapping or web-facing. With our conversion process, your applications will be transformed into true Web applications very quickly. All of your converted screens will be completely customizable with no ties to the original Display Files and no limitations of green-screens.
^ Back to top ^

Integrated Source Control & Change Management
RPGsp includes change management exit points and an integrated multi-user source control system to prevent developers from stepping on each others' toes as they work on Web applications, green-screen programs, and modernization projects. Source code is checked in and out within the RPGsp IDE using a simple point-and-click interface.
^ Back to top ^

A Smart Investment
You will never have to worry about hidden costs, lengthy training, and lack of support. Join the thousands of satisfied clients around the world who already rely on our state-of-the-art tools and industry-leading technical support. Leverage your existing assets, deploy your projects quickly, and be productive from day one with RPGsp.
^ Back to top ^

Backed by an Industry Leader
Profound Logic Software is a proven provider of the best tools, services, and support for System i Web development projects. We have been developing modern System i Web applications and tools for years. After countless successful implementations of our technology and multiple awards for innovation, we have again and again proven that we have what it takes to effectively modernize and add value to AS400, iSeries, and i applications. Profound Logic's impressive list of System i customers further demonstrates our capacity to deliver outstanding results with our products and services. Once you engage with Profound Logic, you will immediately notice our superb level of support and our commitment to providing the best modernization solutions for the System i.

What is IBM i Access for Web

2010-04-02T00:56:00.001+01:00

What is IBM i Access for Web

IBM i Access for Web offers browser-based access to IBM i. IBM i Access for Web enables end users to leverage business information, applications, and resources across an enterprise by extending the IBM i resources to the client desktop through a web browser.

See the Customer Comments on IBM i Access products!

IBM i Access for Web...
is system based; there is no code running on the desktop.
is implemented using Java Servlet technology.
uses industry standard protocols - HTTP, HTTPS and HTML.
is lightweight, requiring only a browser on the client.
runs batch commands, provides access to database, integrated file system, printers, printer output, and messages, and a 5250 interface.

V5R4 iSeries Access for Web is supported on systems with V5R4 and V5R3 i5/OS TM. V5R3 iSeries Access Family (5722-XW1) customers can acquire V5R4 iSeries Access for Web and stay at V5R3 i5/OS. Refer to Ordering/Upgrading.
V5R4 and V5R3 iSeries Access for Web servlets are supported with these web application systems. Refer to the service pack PTFs page for PTF requirements:
Web application system integrated with i5/OS (V5R4 only)
WebSphere Application Server (WAS) - Express V6.1 for i5/OS, WAS V6.1 for i5/OS, and WAS V6.1 Network Deployment for i5/OS
WAS - Express V6.0 for OS/400 and WAS V6.0 for OS/400
WAS - Express for iSeries V5.1 and V5.0
WAS for iSeries V5.1 and V5.0 (Base and Network Deployment Editions)
Apache Software Foundation's Jakarta Tomcat (included with the IBM HTTP Server)

In addition to the above, the IBM i Access for Web portlet code can be used with any of the following portal systems:
IBM Workplace Services Express V2.6 and V2.5
WebSphere Portal for Multiplatforms V6.0
WebSphere Portal for Multiplatforms V5.1.0.1
WebSphere Portal Express for Multiplatforms V5.0.2
WebSphere Portal Express Plus for Multiplatforms V5.0

what is websmart

More details on IBM i Access for Web to follow...

What is WebSmart

2010-04-02T00:50:00.000+01:00

What is WebSmart

WebSmart is the Proven & Award Winning System i & multi-platform rapid Web development tool, from BCD. WebSmart comes in two editions:

WebSmart ILE helps you produce native System i-centric CGI web applications that access DB2400, MS SQL and MySql databases. The apps run in the native Apache HTTP web server shipped with every System i.

WebSmart PHP helps you produce PHP applications that run on multiple platforms- System i, Windows, Linux or Unix and access databases such as DB2/400, MySQL and others.

Both editions of WebSmart let you extend or develop new web applications for any industry or application. You can create B2B, B2C and e-Commerce sites including on-line ordering, inquiries and maintenance programs, and implement browser-based or SOA (web services) applications. And WebSmart fully supports AJAX so you can build rich web content applications that behave like Windows apps.

If you are looking for a popular alternative to IBM’s WebSphere, then take a close look at WebSmart as it is significantly easier to learn and uses way fewer resources than WebSphere.

WebSmart Highlights

Rapid New Web Development
Modernize Legacy Apps
Multi-Platform: ILE CGI or PHP
Access non-iSeries based data bases like MySQL and MSSQL
Visual HTML Editing
Robust Enterprise Apps
Productive IDE for RPG and non-RPG Programmers
Web 2.0 features such as Web Services, SOX, AJAX, etc
Change Management
Free Trials with Unlimited Support
IBM distributes WebSmart globally with V5R4 and new System i sales
Integrated Visual Debugger
Charts and Graphs with Free SmartCharts
SQL Support
Professional Services
Free License: Nexus Portal & ECM. Secure framework for Apps, Docs, Dashboards…
Integrated real-time web Clover Query tool for end-users and developers.
Proven with 1,750+ customers, 1,500,000 users and 13 Industry Awards
Ideal for Small, Medium and Large organizations – Immediate Results

AS400 Analyst Programmer - Dublin

2010-03-27T17:46:00.001Z

AS400 Analyst Programmer

Contract
Immediate contract requirement for an experienced AS400 Analyst to work in a large Bank in Dublin City. AS400 RPG IV, RPGILE and CL Development.
Role:
Write and design technical specifications.
Write and execute unit test scripts, system test strategy and scripts.
Write code changes in RPGILE on development AS400.
Skills:
At least 10 years RPG IV experience.
Previous experience of financial systems, working within the banking sector is required.
If you would like to apply for this role and would like to hear more about this opportunity please email your CV to (see below)
Location Dublin, Ireland
Country Ireland
Start Date ASAP
Duration 6 months
Rate Market rates in Euro.
Employment Business CPL Solutions
Contact Janet Smullen
Email Janet.Smullen.5CF1F.98727@mail.jobserve.com
Reference JS98179
Posted Date 24/03/2010 15:19:04

as400 sbmjob

as400 journalling

AS400 journalling

2010-03-27T16:29:00.002Z

AS400 journalling

How many sites use as400 journalling in their applications. Seems to be that a lot of as400 developers dont actually understand journalling and the data integrity and audit capabilities it can add to an enterprise level system.

The DB2 UDB for AS400 journalling support supplies an audit trail and forward and backward recovery. Forward recovery can be used to take an older version of a table and apply the changes logged on the journal to the table. Backward recovery can be used to remove changes logged on the journal from the table.

When an SQL collection is created, a journal and journal receiver are created in the collection. When SQL creates the journal and journal receiver, they are only created on a user auxiliary storage pool (ASP) if the ASP clause is specified on the CREATE COLLECTION or the CREATE SCHEMA statement. However, because placing journal receivers on their own ASPs can improve performance, the person managing the journal might want to create all future journal receivers on a separate ASP.

When a table is created into the collection, it is automatically journaled to the journal DB2 UDB for AS/400 created in the collection (QSQJRN). A table created in a non-collection will also have journaling started if a journal named QSQJRN exists in that library. After this point, it is your responsibility to use the journal functions to manage the journal, the journal receivers, and the journaling of tables to the journal. For example, if a table is moved into a collection, no automatic change to the journaling status occurs. If a table is restored, the normal journal rules apply. That is, if the table was journaled at the time of the save, it is journaled to the same journal at restore time. If the table was not journaled at the time of the save, it is not journaled at restore time.

The journal created in the SQL collection is normally the journal used for logging all changes to SQL tables. You can, however, use the system journal functions to journal SQL tables to a different journal. This may be necessary if a table in one collection is a parent to a table in another collection. This is because DB2 UDB for AS/400 requires that the parent and dependent file in a referential constraint be journaled to the same journal when updates or deletes are performed to the parent table.

A user can stop journaling on any table using the journal functions, but doing so prevents an application from running under commitment control. If journaling is stopped on a parent table of a referential constraint with a delete rule of NO ACTION, CASCADE, SET NULL, or SET DEFAULT, all update and delete operations will be prevented. Otherwise, an application is still able to function if you have specified COMMIT(*NONE); however, this does not provide the same level of integrity that as400 journalling and commitment control provide

as400 sbmjob

as400 prtf report layout utility

AS400 PRTF - Report Layout Utility

2010-03-27T16:18:00.001Z

AS400 PRTF - Report Layout Utility

The report layout utility (RLU), AS400 licensed program, allows you to create and edit source members on the AS/400 system. RLU source members in source physical
files contain the printer file Data Description Specifications (DDS) for a report
design that you lay out by using RLU.

The report design looks like an actual listing
you generate with a high-level-language (HLL) program. Using RLU, you specify
the information required for DDS, and RLU creates or changes the source member.
The DDS uses keywords to define your report design. Keywords associated with a
field are called field-level keywords, keywords associated with a record are called
record-level keywords, and keywords associated with an entire printer file are called
file-level keywords.

You can perform the following tasks with RLU:
¹ Design a report by defining it on the display, saving it as DDS source, and creating
a printer file.
¹ Create a prototype of a report by printing the as400 prtf report design at any time to make
sure that the reports looks the way you want.

as400 sbmjob

AS400 SBMJOB examples

2010-03-27T06:44:00.001Z

Examples for as400 SBMJOB

Example 1: Submitting an as400 Job

SBMJOB JOB(SPECIAL) JOBD(MYLIB/MYJOBD)
CMD(CALL MYPROG)
This as400 sbmjob command causes the job named SPECIAL to be submitted. Most of the attributes for the job are taken from the job description MYJOBD, or the job that is currently running, except for the command. The CALL command is placed on the submitted job's message queue so that the program MYPROG can be called and run later.

Example 2: Submitting an as400 Job

SBMJOB JOB(PAYROLL) JOBD(PAYROLL) INQMSGRPY(*RQD)
This as400 sbmjob command submits a job named PAYROLL to the system. All the information needed for this job (such as the job queue and routing data but not the inquiry message control value) is contained in the job description PAYROLL, or the job that is currently running. The library list in effect for the job issuing this command is used to find the job description. All inquiry messages sent during running of this job requires the receiver of the inquiry message to reply.

Example 3: Submitting an as400 Job to a Job Queue

as400 subsystem

SBMJOB JOBD(*USRPRF) JOB(COPY12) JOBQ(NIGHTQ)
CMD(CPYF FILEA FILEB)
This as400 sbmjob command submits the job COPY12, which uses the job description in the user profile of the submitting job, to the job queue NIGHTQ. The CMD parameter provides the CL command necessary for the job to run. An as400 sbmjob command such as this might be used to copy the file at night while the system is unattended.

as400 subsystem

2010-03-27T06:33:00.001Z

An as400 subsystem is described by IBM as follows

The subsystem is where work is processed on the system. A subsystem is a single, predefined operating environment through which the system coordinates the work flow and resource use. The system can contain several subsystems, all operating independently of each other. Subsystems manage resources.

All jobs, with the exception of system jobs, run within subsystems. Each subsystem can run unique operations. For instance, one subsystem may be set up to handle only interactive jobs, while another subsystem handles only batch jobs. Subsystems can also be designed to handle many types of work. The system allows you to decide the number of subsystems and what types of work each subsystem will handle.

The run-time characteristics of a subsystem are defined in an object called a subsystem description. For example, if you want to permanently change the amount of work (number of jobs) coming from a job queue into a subsystem you only need to change the job queue entry in the subsystem description.

The controlling subsystem
The controlling subsystem is the interactive subsystem that starts automatically when the system starts, and it is the subsystem through which the system operator controls the system via the system console. It is identified in the Controlling subsystem/library (QCTLSBSD) system value.

IBM® supplies two complete controlling subsystem descriptions: QBASE (the default controlling subsystem) and QCTL. Only one controlling subsystem can be active on the system at any time.

When the system is in the restricted condition, most of the activity on the system has ended, and only one workstation is active. The system must be in this condition for commands such as Save System (SAVSYS) or Reclaim Storage (RCLSTG) to run. Some programs for diagnosing equipment problems also require the system to be in a restricted condition. To end this condition, you must start the controlling subsystem again.

Note: There is also a batch restricted state in which one batch job can be active.
When all of the subsystems, including the controlling subsystem are ended, a restricted condition is created. You can end each subsystem individually or you can use the ENDSBS SBS(*ALL) OPTION(*IMMED).

Important: The system cannot reach the restricted state until there is only one job remaining in the controlling subsystem. Sometimes it may appear as though there is a single job remaining, but the system does not go into the restricted state. In this case you need to verify that there are no suspended system request jobs, suspended group jobs, or disconnected jobs on the remaining active display. Use the Work with Active Jobs (WRKACTJOB) command and press F14=Include to display any suspended or disconnected jobs. If these jobs exist, you need to end them in order for the system to reach the restricted state. The ENDSYS and ENDSBS functions will send a CPI091C information message to the command issuer when this condition is detected.

Subsystem description
A subsystem description is a system object that contains information defining the characteristics of an operating environment controlled by the system. The system-recognized identifier for the object type is *SBSD. A subsystem description defines how, where, and how much work enters a subsystem, and which resources the subsystem uses to perform the work. An active subsystem takes on the simple name of the subsystem description.

Like a set of detailed blueprints, each subsystem description is unique, containing the specific characteristics that describe the subsystem. The description includes where work can enter the subsystem, how much work the subsystem can handle, how much main storage (memory) will be used, and how quickly jobs in the subsystem can run.

You can use a subsystem description supplied with your system (with or without making changes to it), or you can create your own.

Subsystem description attributes
Subsystem description attributes are common overall system attributes. When you create a subsystem, the first step is to define the subsystem attributes.

Work entries
Work entries identify the sources where jobs can enter a subsystem. Specific types of work entries are used for different types of jobs. Work entries are part of the subsystem
description.

ibm as400 manuals v5r4

Routing entries
The routing entry identifies the main storage subsystem pool to use, the controlling program to run (typically the system-supplied program QCMD), and additional run-time information (stored in the class object). Routing entries are stored in the as400 subsystem description.

ibm as400 manuals v5r4

2010-03-24T19:43:00.001Z

IBM AS400 Manuals v5r4.

This is a comprehensive listing of all the as400 manuals that are available as PDFS in the IBM Infocenter

8260 ATM Product Architecture
Administer iSeries Access for Windows
Advanced Functions and Administration on DB2 Universal Database for iSeries
AFP Utilities for iSeries User's Guide
Alerts Support
All You Need to Know When Migrating from IBM Firewall for AS/400
AnyMail/400 Mail Server Framework Support
APPC, APPN, and HPR
APPC Programming
Application Administration
Application Display Programming
Application programming interfaces
AS/400e Diagnostic Tools for System Administrators: An A to Z Reference for Problem Determination
AS/400 Applications: A Fast and Easy Way to Install, Set Up and Work with VRPG and CODE/400 (ADTS CS)
AS/400 Applications: Moving to the 21st Century
AS/400 APPN Configuration Guide
AS/400 Disk Storage Topics and Tools
AS/400 e-commerce: Internet Connection Servers
AS/400 Electronic-Mail Capabilities
AS/400 HTTP Server Performance and Capacity Planning
AS/400 Internet Security: Developing a Digital Certificate Infrastucture
AS/400 Internet Security: Implementing AS/400 Virtual Private Networks
AS/400 Internet Security: Protecting Your AS/400 from HARM in the Internet
AS/400 Internet Security Scenarios: A Practical Approach
AS/400 Performance Explorer Tips and Techniques
AS/400 Performance Management V3R6/V3R7
AS/400 Programming with VisualAge for RPG
AS/400 Remote Journal Function for High Availability and Data Replication
AS/400 Server Capacity Planning
AS/400 TCP/IP Autoconfiguration: DNS and DHCP Support
AS/400 XML in Action: PDML and PCML
ASCII Work Station Reference
Asynchronous Communications Programming
Asynchronous Transfer Mode (ATM) Technical Overview
ATM Configuration Examples
Availability roadmap
A Comprehensive Guide to Virtual Private Networks, Volume III: Cross-Platform Key and Policy Management
A DB2 Enterprise Query Environment -- Build It with QMF for Windows!
A Fast Path to AS/400 Client/Server Using AS/400 OLE DB Support
Backing up your system
Backup, Recovery, and Media Services (BRMS)
Backup and Recovery
Backup Recovery and Media Services for iSeries
Backup Recovery and Media Services for OS/400: A Practical Approach
Basic printing
Basic system operations
BOOTP
Bringing PHP to Your IBM eServer iSeries Server
BSC Equivalence Link Programming
Building AS/400 Applications for IBM WebSphere Standard Edition 2.0
Building AS/400 Internet-Based Applications with Java
Building iSeries Applications for WebSphere Advanced Edition 3.5
Building Java Applications for the iSeries Server with VisualAge for Java 3.5
C/C++ Legacy Class Libraries Reference
CICS Family: API Structure
CICS Family: Interproduct Communication
CICS for iSeries Administration and Operations Guide
CICS for iSeries Application Programming Guide
CICS for iSeries Intercommunication
CICS for iSeries Problem Determination
Clustering and IASPs for Higher Availability on the IBM eServer iSeries Server
Clusters
Commitment control
Common Information Model
Communications Management
Controlling system shutdown using a power-handling program
Control language (CL)
Control panel
Cryptographic Support/400
Cryptography
Customer service and support
Database administration
Database file management
Database overview
Database programming
Database troubleshooting
DB2 Multisystem
DB2 UDB/WebSphere Performance Tuning Guide
DB2 UDB for AS/400 Object Relational Support
DB2 UDB for AS/400 Visual Explain: Illustrating the Secrets
DB2 Universal Database Extenders for iSeries: Text Extender Administration and Programming
DB2 Universal Database Extenders for iSeries: XML Extender Administration and Programming Version 8
DB2 Universal Database Replication Guide and Reference Version 8
DDS concepts
DDS for display files
DDS for ICF files
DDS for physical and logical files
DDS for printer files
Developing iSeries Navigator plug-ins
DHCP
Digital Certificate Manager
Disk management
Distributed database programming
Distributed data management
Distribute software
Domain Name System
Domino for iSeries Sizing and Performance Tuning
DSNX Support
Electronic Service Agent for iSeries User's Guide
E-mail
Embedded SQL programming
Enterprise Identity Mapping (EIM)
Ethernet
Experience reports
Exploring NFS on AS/400
Extensible Markup Language
Finance Communications Programming
Frame relay
FTP
GDDM Programming Guide
GDDM Reference
Getting to know iSeries Navigator
Get started with iSeries communications
Hierarchical Storage Management
High Availability on the AS/400 System: A System Manager's Guide
i5/OS globalization
i5/OS maximum capacities
i5/OS PASE
i5/OS PASE shells and utilities
IBM 8265 Nways ATM Campus Switch
IBM AS/400 Printing V
IBM Content Manager for iSeries: Application Programming Guide and Reference
IBM Content Manager for iSeries: Getting Started with Client for Windows
IBM Content Manager for iSeries: Messages and Code
IBM Content Manager for iSeries: Planning and Installing
IBM Content Manager for iSeries: System Administration Guide
IBM Content Manager for iSeries: Understanding Advanced Workflow
IBM Content Manager OnDemand for iSeries Administration Guide
IBM Content Manager OnDemand for iSeries Common Server Administration Guide
IBM Content Manager OnDemand for iSeries Common Server Indexing Reference
IBM Content Manager OnDemand for iSeries Common Server Planning and Installation Guide
IBM Content Manager OnDemand for iSeries Common Server Web Enablement Kit Installation Guide
IBM Content Manager OnDemand for iSeries Installation Guide
IBM Content Manager OnDemand User's Guide
IBM Content Manager OnDemand Windows Client Customization Guide
IBM Developer Kit for Java
IBM Directory Server for iSeries (LDAP)
IBM eServer i5, iSeries, and AS/400e System Builder IBM i5/OS Version 5 Release 3 October 2004
IBM eServer i5 and iSeries System Handbook: IBM i5/OS Version 5 Release 3 October 2004
IBM eServer iSeries Independent ASPs: A Guide to Moving Applications to IASPs
IBM eServer iSeries Migration: System Migration and Upgrades at V5R1 and V5R2
IBM eServer iSeries Pocket Handbook: Version 5 Release 2 January 2003
IBM eServer iSeries Printing VI: Delivering the Output of e-business
IBM eServer iSeries Universal Connection for Electronic Support and Service
IBM eServer iSeries Wired Network Security: OS/400 V5R1 DCM and Cryptographic Enhancements
IBM HTTP Server (powered by Apache): An Integrated Solution for IBM eServer iSeries Servers
IBM HTTP Server for i5/OS
IBM Infoprint Fonts: Font Summary
IBM Infoprint Fonts: Introduction to Type Transformer and Utilities for Windows
IBM Infoprint Fonts: Japanese Font Library Technical Reference
IBM Infoprint Fonts: Korean Font Library Technical Reference
IBM Infoprint Fonts: Simplified Chinese Font library Technical Reference
IBM Infoprint Fonts: Traditional Chinese Font Library Technical Reference
IBM iSeries eServer IP Networks: Dynamic!
IBM Open Class Library Transition Guide
IBM Telephone Directory V5.2
IBM Toolbox for Java
IBM WebSphere Development Studio Client for iSeries Product Overview
IBM WebSphere V5.0 Security WebShpere Handbook Series
IBM Welcome Page V1.1
ICF Programming
IDDU Use
ILE Application Development Example
ILE C/C++ Compiler Reference
ILE C/C++ for AS/400 MI Library Reference
ILE C/C++ Programmer's Guide
ILE C/C++ Run-time Library Functions
ILE Concepts
Implementation and Practical Use of LDAP on the eServer iSeries Server
Infoprint Fonts: Creating User Defined Characters
Infoprint Server for iSeries: Introduction and Planning Guide
Infoprint Server for iSeries: User's Guide
Inside APPN and HPR - The Essential Guide to New SNA
Install, upgrade, or delete i5/OS and related software
Installing, upgrading, or deleting i5/OS and related software
Integrated file system
Integrating XML with DB2 XML Extender and DB2 Text Extender
Internetworking over ATM: An Introduction
Internetwork Packet Exchange (IPX) Support
Intrasystem Communications Programming
Introduction to Storage Area Networks
Intrusion detection
IP filtering and network address translation
iSeries Access for Linux
iSeries Access for Web
iSeries Access for Windows: Installation and setup
iSeries Access for Windows: Programming
iSeries Guide to Output
iSeries in Storage Area Networks: A Guide to Implementing FC Disk and Tape with iSeries
iSeries Navigator for Wireless
iSeries Navigator tasks on the Web
iSeries NetServer
iSeries Query Manager
iSeries Safety Inspection
iSeries Security Reference
iSeries Service Functions
iSeries Setting Up Your 0578, 5074, 5078 or 5079 Expansion Unit
iSeries Setting Up Your 0588, 0595, 5088, 5094, 5095, or 5294 Expansion Unit
iSeries Setting Up Your 5065 or 5066 Expansion Unit
iSeries Setting up your 5075 Expansion Unit
iSeries Setting Up Your Twinaxial System
iSeries System Debugger
Java and WebSphere Performance on IBM eServer iSeries Servers
Job Scheduler for OS/400
Journal management
LAN, Frame-Relay and ATM Support
Linux in a logical partition
Linux on an integrated xSeries solution
Linux on the IBM eServer iSeries Server: An Implementation Guide
Local Device Configuration
Logical partitions
Lotus Domino for AS/400 Internet Mail and More
Lotus Fax for Domino for AS/400: Getting the Straight Facts
Lotus Notes and Domino R5.0 Security Infrastructure Revealed
LPAR Configuration and Management Working with eServer iSeries Logical Partitions
Maintaining and managing i5/OS and related software
Management Central
Managing AS/400 V4R4 with Operations Navigator
Managing OS/400 with Operations Navigator V5R1 Volume 1: Overview and More
Managing OS/400 with Operations Navigator V5R1 Volume 2: Security
Managing OS/400 with Operations Navigator V5R1 Volume 3: Configuration and Service
Managing OS/400 with Operations Navigator V5R1 Volume 4: Packages and Products
Managing OS/400 with Operations Navigator V5R1 Volume 5: Performance Management
Managing OS/400 with Operations Navigator V5R1 Volume 6: Networking
Microsoft Windows Server 2003 Integration with iSeries
Migrating Applications from WebSphere Application Server Standard Edition to WebSphere Application Server-Express V5
Migration
Migration Options for OS/2 Warp Server for AS/400 and OS/400 Integration for Novell NetWare
MQSeries Backup and Recovery
MQSeries Version 5 Programming Examples
Multithreaded applications
NetWare on iSeries
Networking scenarios
Network authentication service
New Enterprise Integration Functions for Lotus Domino for AS/400
Object signing and signature verification
Operations Console
Optical device programming
OptiConnect
OS/400 Maximum Capacities - V5R2
OS/400 Network File System Support
OS/400 V5R2 Virtual Private Networks: Remote Access to the IBM eServer iSeries Server with Windows 2000 VPN Clients
Performance
Performance and query optimization
Performance Tools for iSeries
Planning a backup and recovery strategy
Plan for and set up system security
Programming with VisualAge RPG
Qshell
Quality of service
Query for iSeries Use
Query Management Facility for Windows
Query Management Programming
Query Manager Use
Rack Lift Tool Operation and Maintenance
Remote Access Services: PPP connections
Remote Work Station Support
REXEC
REXX/400 Programmer's Guide
REXX/400 Reference
Roadmap to Availability on the iSeries 400
RouteD
Secure Sockets Layer (SSL)
Service tools user IDs and passwords
Simple Network Management Protocol (SNMP) Support
Simple Network Time Protocol (SNTP)
Single signon
Slicing the AS/400 with Logical Partitioning: A How to Guide
SNA and TCP/IP Integration
SNA Upline Facility Programming
Socket programming
Speak the Right Language with Your AS/400 System
Spooled files
SQL Call Level Interface (ODBC)
SQL messages and codes
SQL programming
SQL reference
Standard C++ Library Reference
Storage solutions
Stored Procedures, Triggers and User Defined Functions on DB2 Universal Database for iSeries
Striving for Optimal Journal Performance on DB2 Universal Database for iSeries
Subarea to APPN Migration: HPR and DLUR Implementation
System/36-AS/400 Command Cross-Reference
System/36 Environment Programming
System/36 Environment Reference
System/38 Environment Programming
System i and Internet security
System i Performance Capabilities Reference
System Manager Use
System values
Tape files
TCP/IP routing and workload balancing
TCP/IP setup
TCP/IP troubleshooting
TCP/IP Tutorial and Technical Overview
Telnet
TFTP
The AS/400 NetServer Advantage
The IBM Total Storage Tape Libraries Guide for Open Systems
The System Administrator's Companion to AS/400 Availability and Recovery
The XML Files: Using XML for Business-to-Business and Business-to-Consumer Applications
Time management
Token ring
Troubleshooting
Troubleshooting IBM LAN/ATM Campus Networks
Understanding LDAP -- Design and Implementation
Universal Connection
Unleashing AS/400 Applications on the Internet
Upgrades
Using AS/400 Database Monitor and Visual Explain to Identify and Tune SQL Queries
Using LDAP for Directory Integration
Using Sun TI-RPC to develop distributed applications
Using the AS/400 as an IPX Router
V4 TCP/IP for AS/400: More Cool Things Than Ever
Virtual private networking (VPN)
VisualAge RPG Language Reference
VisualAge RPG Parts Reference
WebSphere Application Server for i5/OS V6
WebSphere Application Server for iSeries
WebSphere Application Server - Express for iSeries V5
WebSphere Application Server - Express for iSeries V5.1
WebSphere Application Server - Express V5.0.2 Developer Handbook
WebSphere Application Server - Express V5.0 for iSeries
WebSphere Development Studio: ILE C/C++ Language Reference
WebSphere Development Studio: ILE COBOL Programmer's Guide
WebSphere Development Studio: ILE COBOL Reference
WebSphere Development Studio: ILE RPG Programmer's Guide
WebSphere Development Studio: ILE RPG Reference
WebSphere J2EE Application Development for the IBM eServer iSeries Server
Websphere V3 Performance Tuning Guide
Web Enabling AS/400 Applications with IBM WebSphere Studio
Who Knew You Could Do That with RPG IV? A Sorcerer's Guide to System Access and More
Windows environment on iSeries
Workstation Customization Programming
Work management
X.25 Network Support
XML Toolkit for iSeries

as400 query

Creating an as400 Query

2010-03-21T22:43:00.002Z

Creating an as400 Query

As400 Query, QUERY/400 as it used to be called or IBM Query for Iseries, which is whats shown these days on the Installed Licensed Programs screen (GO LICPGM Option 10) is probably one of the most widely used tools on the as400. This tool has a very straightforward user interface, so is often used by both technical and non technical staff (with relevant training of course). Its a very easy to use tool for displaying, extracting and reporting on data. Query is a separate chargeable product, but I don’t think I have ever worked at a site that didn’t have it installed on all their systems, so you can be pretty sure almost every AS/400 will have the IBM provided query language QUERY/400.

As an example, we will write a query over a typical database file that almost every business system has, the CUSTOMER master file. After extracting the data we will create a report.
At the as400 command line type in WRKQRY and hit ENTER:

----------------------------------------------------------------
Work with Queries

Type choices, press Enter.

Option . . . . . . 1=Create, 2=Change, 3=Copy, 4=Delete
5=Display, 6=Print definition
8=Run in batch, 9=Run
Query . . . . . . . Name, F4 for list
Library . . . . . QGPL Name, *LIBL, F4 for list
-----------------------------------------------------------------

We will create a query to view the data in the CUSTOMER master file. Type in 1 for the option to create a query and the press ENTER.

-----------------------------------------------------------------
Define the Query

Query . . . . . . : Option . . . . . : CREATE
Library . . . . : QGPL CCSID . . . . . . : 65535

Type options, press Enter. Press F21 to select all.
1=Select

Opt Query Definition Option
1 Specify file selections
Define result fields
Select and sequence fields
Select records
Select sort fields
Select collating sequence
Specify report column formatting
Select report summary functions
Define report breaks
Select output type and output form
Specify processing options
-----------------------------------------------------------------

Next "Specify file selections". This is already selected by default so just hit ENTER and you will see:

--------------------------------------------------------------
Specify File Selections

Type choices, press Enter. Press F9 to specify an additional
file selection.

File . . . . . . . . . Name, F4 for list
Library . . . . . . QGPL Name, *LIBL, F4 for list
Member . . . . . . . . *FIRST Name, *FIRST, F4 for list
Format . . . . . . . . *FIRST Name, *FIRST, F4 for list

---------------------------------------------------------------
Enter CUSTOMER (or whatever your customer master file is called) as the file you want to query and YOURLIB (replace with your relevant database library) as the Library and press ENTER. Pressing ENTER again will take you back to the Define the Query screen.

The next option down, the Define result fields option, is described thus: “Select this option either to define one or more new fields to
be used as result fields or to see what result fields are already defined for the query. The new fields will hold the results of arithmetic, character, or date and time operations done on other fields in this query”. In this case we don’t need any result fields so we can ignore this option for now.

We do need to select fields that we want to report on. Type 1 next to "Select and Sequence Fields" and press ENTER
You should now see:

----------------------------------------------------------------
Type sequence number (0-9999) for the names of up to 500 fields to
appear in the report, press Enter.

Seq Field Text Len Dec
CUSTN Customer Number 10 0
CUSTNA1 Cust. Name & Address 1 50
CUSTNA2 Cust. Name & Address 2 50
CUSTNA3 Cust. Name & Address 3 50
CUSTNA4 Cust. Name & Address 4 50
CUSTTOWN Customer Town 10
CUSTREPN Customer Report Name 20
LOCCD Location Code 5

More...
F3=Exit F5=Report F11=Display names only F12=Cancel
F13=Layout F20=Renumber F21=Select all F24=More keys
----------------------------------------------------------------

Since the AS/400 Query knows the file you want to see, as you selected it earlier, it has retrieved the fields in the file and listed them for you to choose from.
Weare going to select the following columns:
cust number
cust name and address 1
cust town
location code
We need to enter a number to select each of the fields that we require, so enter a number next to each field, which will determine the order in which they are displayed. Enter 2 next to CUSTNA1, 1 next to CUSTN, 4 next to CUSTTOWN, and 6 next to LOCCD. Press ENTER twice and then you will be back at the definition screen.

as400 QUERY allows you to view the results of the query while you are modifying it, which is handy as it allows you correct any errors there and then

---------------------------------------------------------------
Display Report
Report width . . . . . : 115
Position to line . . . . . Shift to column . . .
....1....+....2....+....3....+....4....+....5....+....6....+....7
Customer Name and Address 1 Town Location
Number Code
000001 000001 Davis, 2 High St London 010
000002 000012 Charles, 1 High St London 010
000003 000015 Fish, 3 High St London 010
000004 000020 Brompton, 4 High St London 010

-----------------------------------------------------------------

This is the first steps to creating a query that shows records on an as400 database file.

The standard IBM CUA window keys are available on this screen. F20 will move the data window to the right, F19 will move the data window back to the left. F21 will split the screen into two mini windows, one fixed and one moveable, so you can view 2 parts of the data similultaneously. F12 to cancel returns to the main definition screen

Next is to take option 1 for Column Formatting to modify the column headings to be more descriptive. This allows you to change them to be more meaningful to the out being produced.

To change the sequencing of the query, type 1 next to "Select Sort Fields". Typing a 1 next to the customer number field will ensure that the data is produced in customer number order. Pressing F5 will allow review of the result of applying the sort to the customer number field.

The next step is to decide which records to select. Enter a 1 next to select records. In this case we only want to select records with a location code of '030'. The screen will look like:

----------------------------------------------------------
Select Records

Type comparisons, press Enter. Specify OR to start each new
Tests: EQ, NE, LE, GE, LT, GT, RANGE, LIST, LIKE, IS, ISN

AND/OR Field Test Value (Field, Number, 'Char
LOCCD EQ '030'

----------------------------------------------------------
Now the extract will only show customers with a location code of '030'.

Now we need to save the query. Pressing F3 and filling in detals give:

-------------------------------------------------------------
Exit this Query

Type choices, press Enter.

Save definition . . . Y Y=Yes, N=No

Run option . . . . . . 3 1=Run interactively
2=Run in batch
3=Do not run

For a saved definition:
Query . . . . . . . TEMPQRY Name
Library . . . . . QGPL Name, F4 for list

Text . . . . . . . . Display CUSTOMER Master File
---------------------------------------------------------------

And to run the query, from an AS400 command line, key in the command to run a query:

RUNQRY QGPL,TEMPQRY

This should show the results for the as400 query.

as400 virtual terminals

2010-03-21T06:20:00.000Z

A virtual terminal is a device that does not have hardware associated with it. It forms a connection between your application and AS/400 applications, representing a physical work station (possibly on a remote system). The OS/400 licensed program manages the virtual terminal, which directs work station I/O performed by an AS/400 application to the virtual terminal. The virtual terminal APIs allow another AS/400 application, called a server program, to work with the data associated with the virtual terminal.

In a distributed systems environment, the requesting program is called a client; the answering program is called a server. The client and server programs may reside on the same AS/400 system or may be distributed between two different systems. The server program generally runs on behalf of (or in conjunction with) the client program. Together, the server program and the client program allow a work station to be supported as if the work station were connected locally, but is in fact a virtual terminal.

as400 jobs - Lead DB2 DBA(Z/OS or AIX or LUW or OS/400) - IP Soft - Bangalore, KA

2010-03-19T20:02:00.000Z

DB2 DBA for IPSoft, one of the fastest growing MSPs in the US. • Schema Design Review, Physical Tablespace Layout• DB2 Server Installation, Database Creation, Alteration, and Setup• DB2 Server Database File Management.Nice to have a IBM Certification

Differences between iseries as400 API QMHLJOBL and QGYOLJBL

2010-03-14T05:25:00.001Z

Differences between iseries as400 QMHLJOBL and QGYOLJBL

The Open List of Job Log Messages (QGYOLJBL) API lists messages from a job log. The returned messages are sorted by their sending date and time unless the message being listed is a reply message to an inquiry, a sender's copy, or a notify type message. When a reply message exists for one of these messages, the reply message is not positioned according to the sending date and time of the reply. The reply message is, instead, listed immediately following the inquiry, the sender's copy, or the notify message that it is associated with

The List Job Log Messages (QMHLJOBL) API lists messages sent to the job message queue of a job. This API gets the requested message information and returns it in a user space in the format specified in the parameter list. The following discusses how the list is sorted for nonbatch jobs and for batch jobs.

When the job whose messages are being listed is not a batch job, the returned messages are sorted by their sending date and time unless the message being listed is a reply message to an inquiry, a sender's copy, or a notify message. If it is a reply message, it is listed immediately following the inquiry, sender's copy, or notify message with which it is associated.

If the last message listed is an inquiry, a sender's copy, or a notify message, the user of the API must call the API again using parameters that would include listing the next later message after the inquiry, sender's copy, or notify message in order to obtain an available reply message.

When the job whose messages are listed is a batch job, the messages are grouped into two categories:

Request messages that have been or are being processed, and the other messages that occurred during the processing of those requests.
Request messages that are yet to be processed, and any diagnostic messages associated with these request messages.
The API treats unprocessed request messages as if they had a sending time later than all the request messages and their associated messages that have been or are being processed. The following two examples describe the sorting further.

For example, if the call to this API specifies to list the messages for a batch job from oldest to newest, the list consists of all requests and their associated messages that have been or are being processed. They are sorted as described above for a job that is not a batch job. They are followed by any request messages and any associated diagnostic messages that have not yet been processed (in the order that they will be processed).

As an opposite example, if the call to this API specifies to list the messages for a batch job from newest to oldest, the list consists of the request messages that remain to be processed. They are in the opposite order that they are processed. They are followed by the request messages that have been or are being processed and their associated messages. These are sorted backward through time as described above for nonbatch jobs.

The generated list replaces any existing information in the user space.

If the user space is not large enough to contain the data to be returned, the user space is increased to the maximum user space size allowed (16MB) or the maximum amount of storage allowed to the user of the API. If this is not large enough to contain the data to be returned, only the number of complete messages that fit in the user space are returned. The information status field in the generic header is set to P (partial but accurate). The user can then resubmit the request from the last message returned to obtain the additional messages. The key of the last message listed for each message queue is provided in the ending message key field in the header portion of the user space.

The maximum messages requested field and the number of fields to return field for each listed message increase the system resources required to create the list. Users of this API should use caution when specifying parameters that list many messages or request many identified fields to be returned for each listed message

The differences between the QGYOLJBL API and the List Job Log Messages (QMHLJOBL) API follow:

The message information for the QGYOLJBL API is returned into a receiver variable instead of a user space.
The request handle parameter was added to the QGYOLJBL API, so that a distinct value is associated with the list. This value ensures that a request for more messages from the list (call QGYGTLE API) is sent to the correct list.
The total records parameter was added to the QGYOLJBL API, so that the caller of the API knows the size of the list from which information can be requested.
The records returned parameter was added to the QGYOLJBL API. Now if the request is for X records and only Y records exist (where Y < X), the requestor is aware that it did not get the number of records requested.
The amount of information returned by the QMHLJOBL API is limited by the size of a user space, approximately 16MB. The list created by the QGYOLJBL API can contain up to 2GB of information

as400 commands and APIs you'll use for handling messages

2010-03-13T14:58:00.003Z

The following list of ibm as400 commands and APIs are used for receiving/sending messages. The APIs can be used in any program, whereas the commands are restricted to CL.

1. SNDPGMMSG. The Send Program Message (SNDPGMMSG) command sends a message to a named message queue or to a call message queue. A call message queue can be the *EXT external message queue or a message queue associated with a call stack entry. Each time a program or procedure is called a new message queue is associated with its call stack entry. The message queue is identified by the name of its associated program or procedure.

2. QMHSNDPM. The Send Program Message (QMHSNDPM) API sends a as400 message to a call message queue or the external message queue. (The external message queue is the part of the job message queue that handles messages between an interactive job and the work station user. It is not associated with a specific call stack entry.) This API allows the current call stack entry to send a message to its caller, a previous caller, or itself.

3. QMHSNDM. The Send Nonprogram Message (QMHSNDM) API sends a message to a nonprogram message queue so your program can communicate with another job or user

4. RCVMSG. The Receive Message (RCVMSG) command is used by a program to receive a message previously sent to a message queue. The RCVMSG command receives messages from a job message queue (a message queue associated with a call stack entry or the external message queue (*EXT)), or from a named message queue. The program can receive a message from a message queue associated with its own call stack entry or from a message queue associated with another call stack entry

5. QMHRCVPM. The Receive Program Message (QMHRCVPM) API receives a message from a call message queue or external message queue and returns information describing the message

6. QMHRCVM. The Receive Nonprogram Message (QMHRCVM) API receives a message from a nonprogram message queue. To receive a message from a program message queue or from the external message queue, see Receive Program Message API.

More tips on handling messages on IBM as400 to follow...

as400 images

As400 Images

2010-03-06T15:02:00.001Z

as400 running the matrix since 1998

AS/400, Running the Matrix since 1988

2010-03-06T14:59:00.002Z

Updating an as400 db2 CLOB with a 64K RPG Variable

2010-02-26T06:03:00.000Z

With most of us working with large amounts of XML data in our interfaces between applications on our as400 systems or with XML data coming from web services running on other systems, we run up against the issue of how to get this data into the database.

This is a fairly straightforward issue to deal with if we are working with java, but if we are working with good old RPG, how do we our XML data into the as400 database. Especially as the record length on a db2 file is restricted to 32K.

We do have a facility for storing large amounts of data in the database, in the form of LOBs(Large Objects). The type we are specifically interested in is the CLOB, as we can store character data such as XML in there.

In theory we should be able to use embedded SQL in our RPG programs to put our XML data into a database clob fields. We can store up to 2Gb of data in our CLOB. Unfortunately we have another issue. Although RPG has a field size maximum of 64K on V5R4 (16M on V6R1 I believe), we have no simple way of getting our 64K of data in out RPG field into our CLOB.

Looking around online there were plenty of examples of how to read data in from a CLOB, and how to save CLOB data to an IFS file. But there was only one example, from Scott Klement, that showed how you could get data from your as400 RPG field into the CLOB.

The way this is achieved is to bypass embedded SQL and use the SQL Call Level Interface directly. The X/Open SQL Call Level Interface is a standard for direct access the a systems SQL Engine without a precompile. It allows access to SQL functions directly through procedure calls to a service program provided by DB2 on the as400. Using the SQL Call Level Interface procedure calls allows you to prepare SQL statements, execute SQL statements, fetch rows of data, and even do advanced functions such as accessing the catalogs, and binding program variables to output columns.

So using the CLI, we can bypass the limitation of embedded SQL, and pass our 64K of data as a host variable using a pointer. An example that shows how to update a CLOB using this method is shown below

/include *libl/qtxtsrc,MGSQLCLI_H

************************************************************************
* updateClob - Update Clob
************************************************************************
P updateClob B Export
D updateClob pi 10i 0
d Id 10i 0 const
d msg 65535A const

D id s 10s 0
D ptr s *
D rc s 10i 0
D msgLen s 10i 0
D msgSize s 10i 0
D env s like(SQLHENV) inz(SQL_NULL_HENV)
d xmsg s 65535A
/Free

xmsg = msg;

// Create an SQL environment & connection handle
SQLAllocEnv(env);
SQLSetEnvAttrI(env:SQL_ATTR_OUTPUT_NTS:
SQL_FALSE:%size(SQLINTEGER) );
SQLSetEnvAttrI(env: SQL_ATTR_ENVHNDL_COUNTER
:SQL_TRUE: %size(SQLINTEGER) );
SQLAllocConnect(env: conn);

// Set Naming Format
SQLSetConnectAttrI(conn: SQL_ATTR_DBC_SYS_NAMING
:SQL_TRUE: %size(SQLINTEGER) );

// Set Commitment Level to *CHG
SQLSetConnectAttrI(conn: SQL_ATTR_COMMIT
:SQL_COMMIT_CHG: %size(SQLINTEGER) );

// Connect to Database
SQLConnect(conn:'*LOCAL':SQL_NTS:*NULL
:SQL_NTS:*NULL:SQL_NTS );

// Create an SQL statement
SQLAllocStmt(conn: stmt );
rc = SQLPrepare(stmt
: 'UPDATE FILE SET mymsg = ? WHERE myid = ?'
: SQL_NTS );

// Assign statement parameters
ptr = %addr(xmsg);
msgLen = %len(xmsg);
msgSize = %size(xmsg);
rc = SQLBindParam(stmt:1:SQL_CLOB:SQL_CLOB:msgSize
:0:ptr:msgLen);

rc = SQLBindParam(stmt:2:SQL_NUMERIC:SQL_NUMERIC
:%len(id):%decpos(id): %addr(id):0);

// Execute Statement
rc = SQLExecute(stmt);

// Free up SQL Resources
SQLFreeStmt( stmt : SQL_DROP );

cleanup();
return rc;

/End-Free
p E
*+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
* Cleanup(): Deallocate/Disconnect SQL CLI handles
*+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
P cleanup B
D cleanup pi
/free
if (stmt <> SQL_NULL_HSTMT);
SQLFreeStmt( stmt : SQL_DROP );
stmt = SQL_NULL_HSTMT;
endif;

if (conn <> SQL_NULL_HDBC);
SQLDisconnect( conn );
SQLFreeConnect( conn );
conn = SQL_NULL_HDBC;
endif;
/End-Free
p E

Updating an as400 db2 CLOB with a 64K RPG Variable

Proactively Manage your Critical System Messages and Resources on the System i

2010-02-11T03:05:00.000Z

Many IT pros struggle to effectively monitor and manage their critical system messages and resources on System i. This webcast provides tips for improving your System i management and explores how you can automate actions to instantly resolve problems across a single system or a multi-system environment. Learn how to monitor your System i from any location via multiple interfaces, including green screen, PC GUI, web browser and handheld device

http://event.on24.com/eventRegistration/EventLobbyServlet?target=lobby.jsp&playerwidth=950&playerheight=680&totalwidth=800&align=left&eventid=190661&sessionid=1&partnerref=bizcard&key=4B3EFC29235408022AFAD0E2114931BB&eventuserid=32990463

Create PDF on iseries spooled files using Zend_PDF and i5 Toolkit for PHP

2010-02-06T14:04:00.000Z

Zend_Pdf is a PDF manipulation framework for PHP available on iseries via the Zend Core. It can help any PHP application dynamically create or modify PDF documents.

Zend_Pdf offers the following features:
Create or load documents
Manipulate pages within a document
Drawing lines, rectangles, polygons, circles, ellipses and sectors, images and rotations
Use of the 14 built-in fonts or TrueType fonts.

include the Zend.pdf framework in your PHP code:
require_once 'Zend/Pdf.php'

Create a PDF class, an instance of the Zend_Pdf object:

$pdf = new Zend_Pdf();

A document can be loaded from a file using the instance:
$pdf = Zend_PDF::load($filename);

Changes to the PDF document can be saved:
$pdf->save($filename, true);

Zend Core for i5/OS includes the i5 Toolkit for PHP. This gives access to i5 function from PHP. i5_spool allows administration of spool files.

Combining this with Zend_PDF will give iseries and i5/os users free coversion of spooled files to PDFs

UDATE and *DATE in AS400 RPG

2010-01-16T19:17:00.000Z

This document clarifies some potential misunderstandings about the semantics of as400 rpg UDATE (6-digit date) and *DATE (8-digit date). Both reserved words retrieve the job date rather than the system date. This has several ramifications, some of which can be easily overlooked:
o
The date retrieved by UDATE/*DATE can be modified using the as400 CL command CHGJOB to change the job date.
o
For interactive jobs, UDATE/*DATE retrieves the date when the interactive session started. Scenario: A user signs on a machine at a date X and stays logged on past midnight (and possibly over several days). The user then runs an interactive RPG program containing UDATE/*DATE. Either of these reserved words will return date X regardless of what the current date is. To reset what the reserved words return, the user must sign off and back on and, therefore, retain a fresh interactive session.
o
For prestart jobs (PJ) and batch immediate jobs (BCI), the date that is returned for a prestart job (PJ) is the date when the job gets started. It is not the time the connection was made.

Note: Prestart jobs are recycled according to the prestart job entry settings ( WRKSBS , Option 5, Option 10). The date the daemon job started is returned for BCI jobs rather than the time the BCI job started.
o
For batch jobs, UDATE/*DATE retrieves the date when the job was submitted to run. Scenario: A user submits on date X a batch job consisting of a CL program which calls an IBM RPG/400 program with UDATE/*DATE in it. In addition, suppose the CL program includes aDLYJOB command which delays the call to the RPG program until past midnight. When the RPG program finally runs, the UDATE/*DATE in it returns date X (the start date of the batch job) rather than X+1 (the date when the RPG program actually starts running). The same behavior continues on should the CL program recursively call itself over multiple days; as400 rpg UDATE/*DATE continues returning date X for the duration of the job.

unzipping a file on the iseries

2009-09-21T10:27:00.001+01:00

as400 iseries Java ajar tool

The ajar tool is an alternative interface to the jar tool that you use to create and manipulate Java(TM) ARchive (JAR) files. You can use the ajar tool to manipulate both JAR files and ZIP files on the as400.

If you need a ZIP interface or UNZIP interface on the iseries, use the ajar tool instead of the jar tool.

The ajar tool lists the contents of JAR files, extracts from JAR files, creates new JAR files, and supports many of the ZIP formats just as the jar tool does. Additionally, the ajar tool supports adding and deleting files in existing JAR files.

The ajar tool is available using the iseries Qshell Interpreter. For more details, see ajar - Alternative as400 Java archive.

How do you re-enable the user id for STRSST when it has been disabled?

2009-09-21T09:57:00.001+01:00

Use the CHGDSTPWD command. Simple!

Connecting from iseries RPG to a web browser

2009-09-21T09:56:00.003+01:00

Use hotspots in your as400 Client Access session to do this

A hotspot is an area in the iseries PC5250 display session window where you can use your left mouse button to execute a command or function. Hotspots are generally used for the following functions:
• To simulate function keys with point-and-click technology
• To execute a macro by clicking on a word on your PC5250 display screen
• To execute a word or string on your PC5250 screen as if you had typed it in as an AS/400 command or option
• To provide a point-and-click facility by simulating the Enter key at the current cursor location
• To interface PC5250 with your Web browser by launching Web sites directly from your as400 OS/400 display session

http://www.mcpressonline.com/networking/general/fire-up-your-mouse-with-pc5250s-hotspots-feature.html

More as400 connectivity tips to follow

Difference between SFLINZ and SFLCLR keyword?

2009-09-21T09:35:00.002+01:00

One effectively sets all the existing subfile records to blanks and zeros, the other removes existing records

SFLINZ (Subfile Initialize) keyword for display files

Use this record-level keyword on the subfile control record format to specify that the OS/400 program is to initialize all records in the subfile on an output operation to the subfile control record format (identified by the SFLCTL keyword). The fields in each subfile record are initialized to blanks for character type fields, to nulls for floating-point type fields, to zeros for other numeric type fields, or to the constant value specified on input-only fields if the DFT keyword is specified.

When the subfile is displayed (on an output operation to the subfile control record), all records in the subfile are displayed with the same value. Any record previously written is overwritten and no longer has its earlier value

SFLCLR (Subfile Clear) keyword for display files

Use this record-level keyword on the subfile control record format so that your program can clear the subfile of all records. This keyword differs from the SFLDLT keyword in that the subfile is not deleted. It differs from the SFLINZ keyword in that after being cleared, the subfile contains no data. Clearing the subfile does not affect the display. However, after being cleared, the subfile contains no active records.

This keyword has no parameters.

When active records already exist in the subfile and all are to be replaced, your program can send an output operation to the subfile control record format after selecting SFLCLR. This clears the subfile and permits your program to write new records to the subfile (by issuing output operations to the subfile record format while incrementing the relative record number). Issuing an output operation to an already active subfile record causes an error message to be returned to your program.

If SFLCLR is in effect on an output operation and no records exist in the subfile, SFLCLR is ignored

IBM iSeries follows in HP 3000 footsteps?

2009-09-21T09:27:00.002+01:00

Start retraining now guys, I think the answer is very much a yes!

http://3000newswire.blogs.com/3000_newswire/2009/08/ibm-iseries-follows-in-3000-footsteps.html

The bottom line is we all need to face the facts of what is happening. IBM i, the OS, is gradually fading away based on IBM not selling it. Since there is no longer an organization to sell IBM i there can be no turn around or return to prominence

the demise of the OS400 community -- and so the iSeries computer line and its vendors -- seems inevitable to Cancilla

"It will simply continue to decline in users and will most definitely be dropped by IBM when the revenue reaches a point where it is no longer feasible to continue supporting it," he wrote in a blog entry last week. Cancilla is getting a strong reaction from iSeries advocates, according to the IT Jungle's Dan Burger. But that probably won't change the sales effort at IBM. This is an aspect of a vendor's disaffection with a platform that was never played out in public for the HP 3000. Right up to the announcement of HP's exit, the vendor and its partners never broached the prospect of HP giving up on the 3000.

But the AS400 (or iSeries or System i) saw a 40 percent decline in sales from '07 to '08, according to the IT Jungle. IBM has reduced the profile of the most i-like parts of the system when it moved System Licensed Internal Code and a Technology Independent Machine Interface into a new Virtualization Engine

iSeries DB2 catalog tables and views

2009-09-21T08:51:00.001+01:00

iSeries catalog tables and views

The iSeries™ catalog includes the following views and tables in the QSYS2 schema:


DB2 UDB for iSeries name Corresponding ANSI/ISO name Description
SYSCATALOGS CATALOGS Information about relational databases
SYSCHKCST CHECK_CONSTRAINTS Information about check constraints
SYSCOLUMNS COLUMNS Information about column attributes
SYSCST TABLE_CONSTRAINTS Information about all constraints
SYSCSTCOL CONSTRAINT_COLUMN_USAGE Information about the columns referenced in a constraint
SYSCSTDEP CONSTRAINT_TABLE_USAGE Information about constraint dependencies on tables
SYSFUNCS ROUTINES Information about user-defined functions
SYSINDEXES  Information about indexes
SYSJARCONTENTS  Information about jars for Java™ routines.
SYSJAROBJECTS  Information about jars for Java routines.
SYSKEYCST KEY_COLUMN_USAGE Information about unique, primary, and foreign keys
SYSKEYS  Information about index keys
SYSPACKAGE  Information about packages
SYSPARMS PARAMETERS Information about routine parameters
SYSPROCS ROUTINES Information about procedures
SYSREFCST REFERENTIAL_CONSTRAINTS Information about referential constraints
SYSROUTINES ROUTINES Information about functions and procedures
SYSROUTINEDEP ROUTINE_TABLE_USAGE Information about function and procedure dependencies
SYSSEQUENCES  Information about sequences
SYSTABLEDEP  Information about materialized query table dependencies
SYSTABLES TABLES Information about tables and views
SYSTRIGCOL TRIGGER_COLUMN_USAGE Information about columns used in a trigger
SYSTRIGDEP TRIGGER_TABLE_USAGE Information about objects used in a trigger
SYSTRIGGERS TRIGGERS Information about triggers
SYSTRIGUPD TRIGGERED_UPDATE_COLUMNS Information about columns in the WHEN clause of a trigger
SYSTYPES USER_DEFINED_TYPES Information about built-in data types and distinct types
SYSVIEWDEP VIEW_TABLE_USAGE Information about view dependencies on tables
SYSVIEWS VIEWS Information about definition of a view

Need to access MS SQL databases from the as400. Use Microsofts JDBC driver

2009-09-21T08:40:00.003+01:00

Overview of the JDBC Driver

The Microsoft SQL Server JDBC Driver is a Java Database Connectivity (JDBC) 4.0 compliant driver that provides robust data access to Microsoft SQL Server 2000, SQL Server 2005, and SQL Server 2008 databases. The JDBC driver can access many of the new features of SQL Server 2005, including database mirroring; the xml, user-defined, and large-value data types; and it supports the new "snapshot" transaction isolation. In addition, the JDBC driver also supports the use of integrated authentication with SQL Server 2000, SQL Server 2005, and SQL Server 2008. Note that the Microsoft SQL Server JDBC Driver version 2.0 can connect to SQL Server 2008 but does not support the new data types or other features that are new in SQL Server 2008.

Using the JDBC Driver
This section provides quick start instructions for making a simple connection to a SQL Server database by using the Microsoft SQL Server JDBC Driver. Before you connect to a SQL Server database, SQL Server must first be installed on either your local computer or a server, and the JDBC driver must be installed on your local computer.

Choosing the Right JAR file

The Microsoft SQL Server JDBC Driver version 2.0 provides sqljdbc.jar and sqljdbc4.jar class library files to be used depending on your preferred Java Runtime Environment (JRE) settings. For more information about which JAR file to choose, see System Requirements for the JDBC Driver.

Setting the Classpath

The JDBC driver is not part of the Java SDK. If you want to use it, you must set the classpath to include the sqljdbc.jar file or the sqljdbc4.jar file. If the classpath is missing an entry for sqljdbc.jar or sqljdbc4.jar, your application will throw the common "Class not found" exception.

The sqljdbc.jar file and sqljdbc4.jar file are installed in the following location:

\sqljdbc_\\sqljdbc.jar

\sqljdbc_\\sqljdbc4.jar

The following is an example of the CLASSPATH statement that is used for a Windows application:

CLASSPATH =.;C:\Program Files\Microsoft SQL Server JDBC Driver\sqljdbc_2.0\enu\sqljdbc.jar

The following is an example of the CLASSPATH statement that is used for a Unix/Linux application:

CLASSPATH =.:/home/usr1/mssqlserverjdbc/Driver/sqljdbc_2.0/enu/sqljdbc.jar

You must make sure that the CLASSPATH statement contains only one Microsoft SQL Server JDBC driver, such as either sqljdbc.jar or sqljdbc4.jar.

Note:
On Windows systems, directory names longer than 8.3 or folder names with spaces may cause problems with classpaths. If you suspect these types of issues, you should temporarily move the sqljdbc.jar file or the sqljdbc4.jar file into a simple directory name such as C:\Temp, change the classpath, and determine whether that addresses the problem.
Applications that are run directly at the command prompt
The classpath is configured in the operating system. Append sqljdbc.jar or sqljdbc4.jar to the classpath of the system. Alternatively, you can specify the classpath on the Java command line that runs the application by using the java -classpath option.

Applications that run in an IDE
Each IDE vendor provides a different method for setting the classpath in its IDE. Just setting the classpath in the operating system will not work. You must add sqljdbc.jar or sqljdbc4.jar to the IDE classpath.

Servlets and JSPs
Servlets and JSPs are run in a servlet/JSP engine such as Tomcat. The classpath must be set according to the servlet/JSP engine documentation. Just setting the classpath in the operating system will not work. Some servlet/JSP engines provide setup screens that you can use to set the classpath of the engine. In that situation, you must append the correct JDBC Driver JAR file to the existing engine classpath and restart the engine. In other situations, you can deploy the driver by copying sqljdbc.jar or sqljdbc4.jar to a specific directory, such as lib, during engine installation. The engine driver classpath can also be specified in an engine specific configuration file.

Enterprise Java Beans
Enterprise Java Beans (EJB) are run in an EJB container. EJB containers are sourced from various vendors. Java applets run in a browser but are downloaded from a Web server. Copy sqljdbc.jar or sqljdbc4.jar to the Web server root and specify the name of the JAR file in the HTML archive tab of the applet, for example, applet ... archive=sqljdbc.jar>.

Making a Simple Connection to a Database

Using the sqljdbc.jar class library, applications must first register the driver as follows:

Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");

When the driver is loaded, you can establish a connection by using a connection URL and the getConnection method of the DriverManager class:

String connectionUrl = "jdbc:sqlserver://localhost:1433;" +
"databaseName=AdventureWorks;user=MyUserName;password=*****;";
Connection con = DriverManager.getConnection(connectionUrl);
In the JDBC API 4.0, the DriverManager.getConnection method is enhanced to load JDBC drivers automatically. Therefore, applications do not need to call the Class.forName method to register or load the driver when using the sqljdbc4.jar class library.

When the getConnection method of the DriverManager class is called, an appropriate driver is located from the set of registered JDBC drivers. sqljdbc4.jar file includes "META-INF/services/java.sql.Driver" file, which contains the com.microsoft.sqlserver.jdbc.SQLServerDriver as a registered driver. The existing applications, which currently load the drivers by using the Class.forName method, will continue to work without modification.

Note:
sqljdbc4.jar class library requires a Java Runtime Environment (JRE) of version 6.0 or later.

Recover or reset QSECOFR passwords

2009-09-21T08:35:00.000+01:00

When IBM ships a server, both a QSECOFR OS/400 user profile and a QSECOFR service tools user ID are supplied. These are not the same. They exist in different locations and are used to access different functions. Your QSECOFR service tools user ID can have a different password from your QSECOFR OS/400 user profile. Service tools user IDs have different password policies than OS/400 user profiles.
If you lose or forget the passwords for both the QSECOFR OS/400 user profile and the QSECOFR service tools user ID, you may need to install your operating system again to recover them. Contact your service provider for assistance. If you know either of these passwords, this information tells you how to recover the password you do not know.
Reset the QSECOFR OS/400 user profile password
If you know the QSECOFR service tools user ID, you can use it to reset the QSECOFR OS/400 user profile to its initial value (QSECOFR). This procedure requires you to perform an initial program load (IPL) on your server. The change does not take affect until after the IPL. Complete the following steps to reset the QSECOFR OS/400 user profile:
Start DST.
Enter the QSECOFR service tools user ID and password on the DST Sign-On display.
Select option 5 (Work with DST environment) from the Use DST menu.
Select option 6 (Work with Service Tools Security Data) from the Work with DST Environment menu. You will see the Work with Service Tools Security Data menu:
+——————————————————————————–+
| Work with Service Tools Security Data |
| System: _____________ |
| Select one of the following: |
| 1. Reset operating system default password |
| 2. Change operating system install security |
| 3. Work with service tools security log |
| 4. Restore service tools security data |
| 5. Save service tools security data |
| 6. Password level |
| Selection |
+——————————————————————————–+
Select option 1 (Reset operating system default password). The Confirm Reset of System Default Password display appears.
Press Enter to confirm the reset. A confirmation message appears telling you that the system has set the operating system password override.
Continue pressing F3 (Exit) to return to the Exit DST menu.
Select option 1 (Exit DST). The IPL or Install the System menu appears.
Select option 1 (Perform an IPL). The system continues with a manual IPL. If you need additional information about performing an IPL, see the Starting and stopping the iSeries topic.
When the IPL completes, return the keylock switch or electronic keystick to the Auto position, if applicable.
Sign on to OS/400 as QSECOFR. Use the CHGPWD command to change the QSECOFR password to a new value. Store the new value in a safe place.
Attention: Do not leave the QSECOFR password set to the default. This is a security exposure because this is the value shipped with every iSeries server and is commonly known.
Reset the QSECOFR service tools user ID and password
If you know the password for the QSECOFR OS/400 user profile, you can use it to reset the password for the IBM-supplied service tools user ID that has service tools security privilege (QSECOFR) to the IBM-supplied default value by completing the following steps:
Ensure that the server is in normal operating mode, not DST.
Sign on at a workstation using the QSECOFR OS/400 user profile.
On a command line, type CHGDSTPWD (Change IBM Service Tools Password). You see the Change IBM Service Tools Password (CHGDSTPWD) display:
+——————————————————————————–+
| Change IBM Service Tools Pwd (CHGDSTPWD) |
| |
|Type choices, press Enter. |
| |
|Password . . . . . . . . . . . . *DEFAULT *SAME, *DEFAULT |
| |
+——————————————————————————–+
Type *DEFAULT and press the Enter key. This sets the IBM-supplied service tools user ID that has service tools security privilege and its password to QSECOFR.
Attention: Do not leave the QSECOFR service tools user ID and password set to the default value. This is a security exposure because this is the value shipped with every iSeries server and is commonly known. See the Recommendations for managing service tools user IDs for more information.

Parsing An Excel Spreadsheet with as400 RPG and Java

2009-09-20T13:15:00.002+01:00

Scott Klement has an article on how to do this on the as400 here...

In the May 15, 2003, issue of Club Tech iSeries Programming Tips, some information was presented on how to use the Jakarta-POI/HSSF Java classes together with an iseries RPG program to create an Excel spreadsheet. In this tip, the same open-source Java classes will be used to do the opposite: to extract data from an existing Excel spreadsheet.

http://www.easy400.net/hssfcgi/documentation/17840.html

The downloadable as400 source code for this tip contains an RPG service program and Java .jar file that work together with the HSSF classes to make parsing an Excel document a snap. All you have to do is provide a as400 rpg subprocedure for character cells and a subprocedure for numeric cells, and the service program will call them back for each cell in the workbook

Unleash the power of i5/os on your windows server using the QNTC File System

2009-09-20T13:08:00.001+01:00

Once you have QNTC configured, and you have a user profile that can perform operations on your target Windows file shares, you can use QNTC to read and write stream file data to a Windows server in the same way you would normally use the root (/) directory of the IFS, the QDLS file system, or the OpenSys IFS file systems in application programs. Your Windows file systems merely become targets for ASCII and stream file operations, which gives you the ability to use your Windows servers to read and update Windows data in OS/400 programs or to back up Windows data to an OS/400-based tape drive by using the Save Object (SAV) command

http://www.itjungle.com/fhg/fhg031704-story04.html

Using Reserved Words in as400 sql queries

2009-09-20T13:00:00.002+01:00

If your trying to run an SQL statement on the as400, but are getting errors because one of your column names is an DB2/400 SQL reserved word, try the following.

Wrap double quotes around the offending column name, and also make it uppercase. This should resolve the reserved words problem!

Locking down and logging iSeries file access from SQL & FTP commands from windows/unix/java environment

2009-09-18T18:13:00.002+01:00

Each server application on the as400, first calls an exit program, if one exists, and then continues to access the data. Eg The exit program for ODBC is QIBM_QZDA_INIT.

The steps to creating an exit program are

Create you exit program

Use WRKREGINF to work with exit programs
Use option 1 to add the program to the list of registered exit programs

This link to an example:

http://publib.boulder.ibm.com/infoce...imstsmprpg.htm


Examples: Create exit programs with RPG

The following example illustrates how to set up a user exit program with RPG*.

Note: Read the Code example disclaimer for important legal information.

 

    **
      ** OS/400 SERVERS - SAMPLE USER EXIT PROGRAM
      **
      ** THE FOLLOWING RPG PROGRAM UNCONDITIONALLY
      ** ACCEPTS ALL REQUESTS. IT CAN BE USED AS A SHELL
      ** FOR SPECIFIC APPLICATIONS. NOTE: REMOVE THE
      ** SUBROUTINES AND CASE STATEMENT ENTRIES FOR THE SERVERS
      ** THAT DO NOT REQUIRE
      ** SPECIFIC EXIT PROGRAM HANDLING FOR BETTER PERFORMANCE.
      **
     E*
     E* NECESSARY ARRAY DEFINITIONS FOR TRANSFER FUNCTION
     E* AND REMOTE SQL
     E*
     E                    TFREQ    4096  1
     E                    RSREQ    4107  1
     I*
     I*
     IPCSDTA      DS
     I                                        1  10 USERID
     I                                       11  20 APPLID
     I*
     I* SPECIFIC PARAMETERS FOR VIRTUAL PRINTER
     I*
     I                                       21  30 VPFUNC
     I                                       31  40 VPOBJ
     I                                       41  50 VPLIB
     I                                       71  750VPIFN
     I                                       76  85 VPOUTQ
     I                                       86  95 VPQLIB
     I*
     I* SPECIFIC PARAMETERS FOR MESSAGING FUNCTION
     I                                       21  30 MFFUNC
     I*
     I* SPECIFIC PARAMETERS FOR TRANSFER FUNCTION
     I*
     I                                       21  30 TFFUNC
     I                                       31  40 TFOBJ
     I                                       41  50 TFLIB
     I                                       51  60 TFMBR
     I                                       61  70 TFFMT
     I                                       71  750TFLEN
     I                                       764171 TFREQ
     I*
     I* SPECIFIC PARAMETERS FOR FILE SERVER
     I*
     I* NOTE: FSNAME MAY BE UP TO l6MB.
     I* FSNLEN WILL CONTAIN THE ACTUAL SIZE OF FSNAME.
     I*
     I                                    B  21  240FSFID
     I                                       25  32 FSFMT
     I                                       33  33 FSREAD
     I                                       34  34 FSWRIT
     I                                       35  35 FSRDWR
     I                                       36  36 FSDLT
     I                                    B  37  400FSNLEN
     I                                       41 296 FSNAME
     I*
     I* SPECIFIC PARAMETERS FOR DATA QUEUES
     I*
     I                                       21  30 DQFUNC
     I                                       31  40 DQQ
     I                                       41  50 DQLIB
     I                                       70  750DQLEN
     I                                       76  77 DQROP
     I                                       78  820DQKLEN
     I                                       83 338 DQKEY
     I*
     I* SPECIFIC PARAMETERS FOR REMOTE SQL
     I*
     I                                       21  30 RSFUNC
     I                                       31  40 RSOBJ
     I                                       41  50 RSLIB
     I                                       51  51 RSCMT
     I                                       52  52 RSMODE
     I                                       53  53 RSCID
     I                                       54  71 RSSTN
     I                                       72  75 RSRSV
     I                                       764182 RSREQ
     I*
     I* SPECIFIC PARAMETERS FOR NETWORK PRINT SERVER
     I*
     I                                       21  28 NPFT
     I                                    B  29  320NPFID
     I* THE FOLLOWING PARAMETERS ADDITIONAL FOR FORMAT SPLF0l00
     I                                       33  42 NPJOBN
     I                                       43  52 NPUSRN
     I                                       53  58 NPJOB#
     I                                       59  68 NPFILE
     I                                    B  69  720NPFIL#
     I                                    B  73  760NPLEN
     I                                       77 332 NPDATA
     I*
     I* Data queue server:
     I*
     I* QIBM_QZHQ_DATA_QUEUE  format ZHQ00100
     I*
     I                                       21  28 DQOFMT
     I                                    B  29  320DQOFID
     I                                       33  42 DQOOBJ
     I                                       43  52 DQOLIB
     I                                       53  54 DQOROP
     I                                    B  55  580DQOLEN
     I                                       59 314 DQOKEY
     I*
     I* Specific PARAMETERS FOR CENTRAL SERVER
     I*
     I                                       21  28 CSFMT
     I                                    B  29  320CSFID
     I* Central server:
     I*
     I* QIBM_QZSC_LM format ZSCL0l00 for license management calls
     I*
     I*
     I                                       33 287 CSLCNM
     I                                      288 295 CSLUSR
     I                                      296 302 CSLPID
     I                                      303 306 CSLFID
     I                                      307 312 CSLRID
     I                                    B 313 3140CSLTYP
     I*
     I* Central server:
     I*
     I* QIBM_QZSC_LM format ZSCS0l00 for system management calls
     I*
     I*
     I                                       33 287 CSSCNM
     I                                      288 542 CSSCMY
     I                                      543 543 CSSNDE
     I                                      544 798 CSSNNM
     I*
 
     I* Central server:
     I*
     I* QIBM_QZSC_LM format ZSCN0l00 for retrive conversion map calls
     I*
     I*
     I                                       21  30 CSNXFM
     I                                       29  320CSNFNC
     I                                    B  33  360CSNFRM
     I                                    B  37  400CSNTO
     I                                    B  41  420CSNCNT
     I*
     I* SPEClFIC PARAMETERS FOR DATABASE SERVER
     I*
     I                                       21  28 DBFMT
     I                                    B  29  320DBFID
     I*
     I* THE FOLLOWING PARAMETERS ADDITIONAL FOR FORMAT ZDAD0l00
     I                                       33 160 DBDFIL
     I                                      161 170 DBDLIB
     I                                      171 180 DBDMBR
     I                                      181 190 DBDAUT
     I                                      191 318 DBDBFL
     I                                      319 328 DBDBLB
     I                                      329 338 DBDOFL
     I                                      339 348 DBDOLB
     I                                      349 358 DBDOMB
     I*
     I* THE FOLLOWING PARAMETERS ADDITIONAL FOR FORMAT ZDAD0200
     I                                    B  33  360DBNUM
     I                                       37  46 DBLIB2
     I*
     I* THE FOLLOWING PARAMETERS ADDITIONAL FOR FORMAT ZDAQ0l00
     I                                       33  50 DBSTMT
     I                                       51  68 DBCRSR
     I                                       69  70 DBOPI
     I                                       71  72 DBATTR
     I                                       73  82 DBPKG
     I                                       83  92 DBPLIB
     I                                    B  93  940DBDRDA
     I                                       95  95 DBCMT
     I                                       96 351 DBTEXT
     I* THE FOLLOWING PARAMETERS REPLACE DBTEXT FOR FORMAT ZDAQ0200
     I                                       96 105 DBSQCL
     I                                    B 133 1360DBSQLN
     I                                      137 392 DBSQTX
     I* THE FOLLOWING PARAMETERS ADDITIONAL FOR FORMAT ZDAR0l00
     I                                       33  52 DBLIBR
     I                                       53  88 DBRDBN
     I                                       89 108 DBPKGR
     I                                      109 364 DBFILR
     I                                      365 384 DBMBRR
     I                                      385 404 DBFFT
 
     I* THE FOLLOWING PARAMETERS ADDITIONAL FOR FORMAT ZDAR0200
     I                                       33  42 DBRPLB
     I                                       43 170 DBRPTB
     I                                      171 180 DBRFLB
     I                                      181 308 DBRFTB 
     I*
     I* Remote command and distributed program call server:
     I*
     I* QIBM_QZRC_RMT  format CZRC0100
     I*    RCPGM AND RCLIB ARE NOT USED FOR REMOTE COMMAND CALLS
     I*
     I                                       21  28 RCFMT
     I                                    B  29  320RCFID
     I                                       33  42 RCPGM
     I                                       43  52 RCLIB
     I                                    B  53  560RCNUM
     I                                       57 312 RCDATA
     I*
     I* signon server:
     I*
     I* QIBM_QZSO_SIGNONSRV format ZSOY0l00 for TCP/IP signon server
     I*
     I                                       21  28 SOXFMT
     I                                    B  29  320SOFID
     I*
     I***************************************************************
     I*
     I              '*VPRT     '          C         #VPRT
     I              '*TFRFCL   '          C         #TRFCL
     I              '*FILESRV  '          C         #FILE
     I              '*MSGFCL   '          C         #MSGF
     I              '*DQSRV    '          C         #DQSRV
     I              '*RQSRV    '          C         #RQSRV
     I              '*SQL      '          C         #SQL
     I              '*NDB      '          C         #NDBSV
     I              '*SQLSRV   '          C         #SQLSV
     I              '*RTVOBJINF'          C         #RTVOB
     I              '*DATAQSRV '          C         #DATAQ
     I              'QNPSERVR  '          C         #QNPSV
     I              '*CNTRLSRV '          C         #CNTRL
     I              '*RMTSRV   '          C         #RMTSV
     I              '*SIGNON   '          C         #SIGN
     I*
     C*
     C* EXIT PROGRAM CALL PARAMETERS
     C*
     C           *ENTRY    PLIST
     C                     PARM           RTNCD   1
     C                     PARM           PCSDTA
     C*
 
     C* INITIALIZE RETURN VALUE TO ACCEPT REQUEST
     C*
     C                     MOVE '1'       RTNCD
     C*
     C* COMMON PROCESSING
     C*
     C*              COMMON LOGIC GOES HERE
     C*
     C* PROCESS BASED ON SERVER ID
     C*
     C           APPLID    CASEQ#VPRT     VPRT
     C           APPLID    CASEQ#TRFCL    TFR
     C           APPLID    CASEQ#FILE     FILE
     C           APPLID    CASEQ#MSGF     MSG
     C           APPLID    CASEQ#DQSRV    DATAQ
     C           APPLID    CASEQ#RQSRV    RSQL
     C           APPLID    CASEQ#SQL      SQLINT
     C           APPLID    CASEQ#NDBSV    NDB
     C           APPLID    CASEQ#SQLSV    SQLSRV
     C           APPLID    CASEQ#RTVOB    RTVOBJ
     C           APPLID    CASEQ#DATAQ    ODATAQ
     C           APPLID    CASEQ#QNPSV    NETPRT
     C           APPLID    CASEQ#CNTRL    CENTRL
     C           APPLID    CASEQ#RMTSV    RMTCMD
     C           APPLID    CASEQ#SIGN     SIGNON
     C                     END
     C                     SETON                     LR
     C                     RETRN
     C*
     C* SUBROUTINES
     C*
     C*
     C* VIRTUAL PRINT
     C*
     C           VPRT      BEGSR
     C*            SPECIFIC LOGIC GOES HERE
     C                     ENDSR
     C*
     C* TRANSFER FUNCTION
     C*
     C* THE FOLLOWING IS AN EXAMPLE OF SPECIFIC PROCESSING
     C* THAT THE EXIT PROGRAM COULD DO FOR TRANSFER FUNCTION.
     C*
 
     C* IN THIS CASE, USERS ARE NOT ALLOWED TO SELECT
     C* DATA FROM ANY FILES THAT ARE IN LIBRARY QIWS.
     C*
     C           TFR       BEGSR
     C           TFFUNC    IFEQ 'SELECT'
     C           TFLIB     ANDEQ'QIWS'
     C                     MOVE '0'       RTNCD
     C                     END
     C                     ENDSR
     C*
     C*
     C* FILE SERVER
     C*
     C           FILE      BEGSR
     C*             SPECIFIC LOGIC GOES HERE
     C                     ENDSR
     C*
     C* MESSAGING FUNCTION
     C*
     C           MSG       BEGSR
     C*             SPECIFIC LOGIC GOFS HERE
     C                     ENDSR
     C* DATA QUEUES
     C*
     C           DATAQ     BEGSR
     C*             SPECIFIC LOGIC GOES HERE
     C                     ENDSR
     C*
     C* REMOTE SQL
     C*
     C           RSQL      BEGSR
     C*             SPECIFIC LOGIC GOES HERE
     C                     ENDSR
     C*
     C* SERVERS
     C*
     C*
     C* DATABASE INIT
     C*
     C           SQLINT    BEGSR
     C*             SPECIFIC LOGIC GOES HERE
     C                     ENDSR
     C*
     C* DATABASE NDB (NATIVE DATABASE)
     C*
     C           NDB       BEGSR
     C*             SFECIFIC LOGIC GOES HERE
     C                     ENDSR
     C*
 
     C* DATABASE SQL
     C*
     C           SQLSRV    BEGSR
     C*             SPECIFIC LOGIC GOES HERE
     C                     ENDSR
     C*
     C* DATABASE RETRIEVE OBJECT INFORMATION
     C*
     C           RTVOBJ    BEGSR
     C*             SPECIFIC LOGIC GOES HERE
     C                     ENDSR
     C*
     C* DATA QUEUE SERVER
     C*
     C           ODATAQ    BEGSR
     C*             SPECIFIC LOGIC GOES HERE
     C                     ENDSR
     C*
     C* NETWORK PRINT
     C*
     C           NETPRT    BEGSR
     C*             SPECIFIC LOGIC GOES HERE
     C                     ENDSR
     C*
     C* CENTRAL SERVER
     C*
     C*
     C* THE FOLLOWING IS AN EXAMPLE OF SPECIFIC PROCESSING
     C* THAT THE EXIT PROGRAM COULD DO FOR LICENSE MANAGEMENT.
     C*
     C* IN THIS CASE, THE USER "USERALL" WILL NOT BE ALLOWED
     C* TO EXECUTE ANY FUNCTIONS THAT ARE PROVIDED BY THE
     C* CENTRAL SERVER FOR WHICH THIS PROGRAM IS A REGISTERED
     C* EXIT PROGRAM - LICENSE INFORMATION, SYSTEM MANAGEMENT
     C* OR RETRIVE A CONVERSION MAP.
     C*
     C           CENTRL    BEGSR
     C           USERID    IFEQ 'USERALL'
     C                     MOVE '0'       RTNCD
     C                     ENDIF
     C*            SPECIFIC LOGIC GOES HERE
     C                     ENDSR
     C*
 
     C* REMOTE COMMAND AND DISTRIBUTED PROGRAM CALL
     C*
     C* IN THIS CASE, THE USER "USERALL" WILL NOT BE ALLOWED
     C* TO EXECUTE ANY REMOTE COMMANDS OR REMOTE PROGRAM CALLS
     C*
     C           RMTCMD    BEGSR
     C           USERID    IFEQ 'USERALL'
     C                     MOVE '0'       RTNCD
     C                     ENDIF
     C                     ENDSR
     C*
     C* SIGNON SERVER
     C*
     C           SIGNON    BEGSR
     C*                  SPECIFIC LOGIC GOES HERE
     C                     ENDSR

Automating a process to run every 10 minutes

2009-09-18T17:58:00.002+01:00

If you need to run a as400 job, say a database query or report on a regular schedule, heres and example of how to do this. Lets say you needed to run a query every 10 mins...

You could submit a CL program, MYJOB to do this, to batch, with a 10 minute delay and a data area to terminate the job externally...

MYJOB:
Loop:
Run database query
Print Report
FTP data
etc

dlyjob 10 minutes
check kill dataarea and exit if set
goto loop

The problem here is that the job will could run for almost 10 minutes after, if the kill data area is set just after its checked. If you operator needs to shut down the system in a hurry you dont want him waiting an extra 10 minutes for a DLYJOB.

A better way to do the is to replace the read of a data area with a read of a data queue. The CL can then wait the required time for a kill entry to appear on the data queue. If it does you end processing runs immediately, if not you core processing runs again, then the check again. The most you will have to wait is the length of time it takes to run your core processing! So no DLYJOB required, just a QRCVDTAQ (and a QSNDDTAQ to set it of course)

MYJOB:
Loop:
Run database query
Print Report
FTP data
etc

check and wait on kill dataqueue for 10 mins and exit if set
goto loop

Using free-form RPG program to call another RPG program

2009-09-18T17:52:00.003+01:00

If you get RNF3751 'External procedure on prototype for main procedure is not the same as actual external name' when trying to call an RPG using free format, check you procedure interface. Your PR and your PI need to match!

eg

For program myrpg01

d myrpg01 pr
d parm 1A

d myrpg01 pi
d parm 1A

then to call

either CALLP myrpg01('MYPARM');

or just

myrpg01('MYPARM');

Trying to find out as400 library size

2009-09-18T17:48:00.003+01:00

To find out your as400 library sizes run

DSPLIB LIB(*All) OUTPUT(*PRINT)

in a batch job.

This will show you the size of all objects in the as400 libraries and the total library size including the objects at the bottom of each library in the report.

Creating an AS/400 passthrough query in MS Access

2009-09-15T22:46:00.002+01:00

Passthrough queries can be efficient for AS/400 ODBC connections because they let you bypass the JET engine and take advantage of the AS/400's query processor.

To create a passthrough query in Access, open the Queries windows and then double-click the "Create query in design view" icon. Close the New Tables dialog box that automatically appears. Then, on the Query menu, select SQL Specific and then Pass-Through option. Next, set the ODBC connection string by selecting the Properties icon in the toolbar and then clicking on the ellipsis next to the ODBC Connect Str property. You're then prompted to select an existing data source to the AS/400, or you can create a new data source if an AS/400 data source doesn't already exist. After setting the connection properties, type your passthrough query in the SQL Pass-Through Query window and click the Execute icon to run the query

Typical settings for MS OLE DB Provider for IBM DB2

2009-09-12T10:27:00.004+01:00

Example settings for configuring MS OLE DB provider for DB2 for as400 iseries


Affiliate Application
Alternate TP Name
APPC Local LU Alias
APPC Mode Name              QPCSUPP
APPC Remote LU Alias
APPC Security Type          Program
Auth Encrypt    False
Cache Authentication        False
Client Application Name 
Connection Pooling          False
Data Source                 myas400.mydomain.com
DateTime As Char            False
DateTime as Date            False
DBMS Platform               DB2/AS400
Default Qualifier
Default Schema              MYDATA (note, this is the library name containing the files to access on as400)
Defer Prepare               False
Derive Parameters           False
Extended Properties  
Host CCSID                  37
Initial Catalog             MY400
Integrated Security
Mode                        ReadWrite
Network Address             myipaddress
Network Port                446
Network Transport Library   TCPIP
New Password
Package Collection          SQLPKG (library to contain the packages created for pulling/pushing data from/to this box)
PC Code Page                1252
Persist Security Info       False
Principle Name
Process Binary as Character false
Rowset Cache Size           0
Units of Work               RUW
Use Early Metadata          False
Locale Identifier           1033
Mode                        3
Protection Level            1
Connection Pooling          false

More as400 settings to follow

Display Command Line Window (QUSCMDLN) API

2009-08-29T12:32:00.000+01:00

The Display Command Line Window (QUSCMDLN) API displays a window containing a command line. A window is an area on the display that is treated as a separate display. Windows have visible boundaries and appear to overlay the display from which they are requested.

The QUSCMDLN API has no parameters

Reno County is preparing to move from an AS400 computer system to a personal-computer-based system

2009-07-24T18:19:00.002+01:00

Information Services director Mike Mathews said the county has operated from the same basic computer platform since 1986, and maintenance and upgrades became concerns

I hope they mean of their software? If they were worried about maintenance and upgrade of their iseries, someone was obviously giving them some very bad advice.

http://www.hutchnews.com/Localregional/flushots2009-07-22T20-54-47

Calling an RPG program from Groovy

2009-07-24T17:41:00.003+01:00

DON DENONCOURT shows how to call RPG from Groovy, via an sql stored procedure call

I've been integrating Java applications with AS400/iSeries/Systemi RPG programs for over ten years. I've covered it in my book (Java Application Strategies for the iSeries) as well as in many of my articles. Calling RPG from Java can be complex. There are 4 or so options but I've been fairly emphatic about using JDBC callable statements as it is the simplest approach. To do that you need to create a stored produce "wrapper" for the RPG. But the Java code still can be quite verbose. Not so with Groov

http://denoncourt.blogspot.com/2009/07/calling-rpg-program-from-groovy.html

"We found out the hard way that turning the terminal off doesn’t necessarily end the job"

2009-07-24T17:13:00.002+01:00

From http://techblog.livingatrandom.com/2005/08/20/newbie-blunders-part-i/

Since this is my first article, I decided to look back at my career. Starting out in 1996 with a small IT company, I was a fresh graduate and like other graduates, I had no idea what an AS/400 (which is what they called the iSeries back then) was. Naturally, I was pretty excited. When I say this big refrigerator in the middle of the room, I said to myself, “Cool! I get to program using a mainframe!” The other trainees and I were told later that day however, that it was a midrange.

“Huh? A mid-what?”

Since our exposure in college was focused on PC’s and DOS (Yeah, yeah, yeah. It was that long ago), we only had a rough idea of what other platforms were. Heck, we thought mainframes belonged to musuems even then. The dumb terminals that were assigned to us were really big…about the size of a microwave oven.

Eventually, the other trainees and I went through…well…training. We were all coding happily one day when one of us suddenly had an endless loop in a piece of code. No problem! Just press Ctrl-C or Ctrl-Break. But how? There isn’t even a Ctrl key!

Since it was almost time to go home anyway, we all suggested to our colleague, “Just turn the terminal off and we’ll go home. You can find the bug tomorrow.”

Imagine our suprise when we were all called down to our boss’ office the following day. We found out the hard way that turning the terminal off doesn’t necessarily end the job. We all were given a long lecture on how to use the System-Request key.

Exploring NFS on AS/400

2009-07-24T17:06:00.002+01:00

This redbook explores the Network File System on the AS400 system.

The OS/400 Network File System (NFS) Support, which was introduced with V3R7 as part of TCP/IP Utility, provides a new system function for the AS400 system that allows you to construct a distributed network system where all users can access the data they need. This redbook will help you use the features of the NFS to share data across sytems. It explains the security considerations to be aware of while using NFS. It then goes on to explore the National Language Support features offered by NFS. Further on, it describes the enhancements in the NFS when compared to the File Server Support/400, which was made available for versions of OS/400 earlier than V3R7. This book also includes the steps involved to migrate from FSS/400 to NFS. The final chapter in this redbook covers a few common problems that you might come across while using the NFS and how to solve them. The intended audiences for this redbook are system administrators building up and maintaining a distributed network using NFS and AS/400 customers or programmers working with the Network File System. It is assumed that the reader has basic working experience with the AS/400 system

Chapter 1. Integrated File System Overview 1.0
Chapter 2. Network File System Overview 2.0
Chapter 3. Operating and Using NFS 3.0
Chapter 4. NFS Security 4.0
Chapter 5. National Language Support 5.0
Chapter 6. Migrating from FSS/400 to NFS 6.0
Chapter 7. Common Problems Encountered in NFS 7.0
Appendix A. Layout and Rules of the /etc/exports File A.0
Appendix B. Layout and Rules of the /etc/netgroup File B.0
Appendix C. NLS Code Page Example C.0
Appendix D. Installation of the Edit File (EDTF) command D.0
Appendix E. CHOWN() API Description E.0
Appendix F. PC NFS Client Considerations F.0
Appendix G. Displaying Exported Files G.0
Appendix H. Special Notices H.0
Appendix I. Related Publications I.0

http://www.redbooks.ibm.com/abstracts/sg242158.html

Network File System on the AS400 system

Common High availability issues in an i5/OS High-Availability and Replication Environment

2009-07-24T17:01:00.002+01:00

Joe Hertvik discusses the issues that can occur once you have you HA and replication environment up and running on your as400.

The second mistake occurs when administrators don't make sure that replicated data stays in sync. Before a failover, perform further auditing on your data groups to make sure that someone hasn't accidentally removed a library from the replication scheme. My shop ran a test last month where we found a critical library was present on both the target and source systems, but its contents hadn't been replicated in six months. Replication had accidentally been turned off; the programs worked but the data was old. So in addition to making sure that you have the same libraries on both systems, make sure that the data is being kept in sync. Otherwise, you may have replicated the file structure perfectly but your data may not be up to date

http://www.itjungle.com/fhg/fhg060309-story03.html

OnDemand SQL Performance Analysis Simplified on DB2 for i5/OS in V5R4

2009-07-24T16:54:00.002+01:00

The goal of database performance tuning is to minimise the response time of your queries. It is also to optimise your servers resources by minimising network traffic, disk IO, and CPU time.
This IBM Redbook helps you to understand the basics of identifying and tuning the performance of Structured Query Language (SQL) statements using IBM DB2 for i5/OS . DB2 for i5/OS provides a comprehensive set of tools that help technical analysts tune SQL queries. The SQL Performance Monitors are part of the set of tools that IBM i5/OS provides for assisting in SQL performance analysis since Version 3 Release 6. These monitors help to analyze database performance problems after SQL requests are run. In V5R4 of i5/OS iSeries Navigator provides a series of new tools to do SQL Performance analysis that we cover in this redbook. Among the new tools that we will covering are:
- Capability of visualizing the contents of the SQE Plan Cache
- SQE Plan Cache Snapshots
- The new reporting tool - Dashboard
- OnDemand Index Advisor
- Evaluators such as Index and Materialized Query Tables
This redbook also presents tips and techniques based on the SQL Performance Monitors and other tools, such as Visual Explain and all the tools provided in V5R4. You’ll find this guidance helpful in gaining the most out of both DB2 for i5/OS and query optimizer when using SQL

Chapter 1. Determining whether you have an SQL performance problem
Chapter 2. DB2 for i5/OS performance basics
Chapter 3. Overview of tools to analyze database performance
Chapter 4. Gathering SQL performance data
Chapter 5. Analyzing SQL performance data using iSeries Navigator
Chapter 6. Custom Database Monitor Analysis
Chapter 7. SQE Plan Cache and SQE Plan Cache Snapshots
Chapter 8. Analyzing database performance data with Visual Explain
Chapter 9. Index Advisor
Chapter 10. SQL Performance Analysis: A Methodology
Chapter 11. Environmental settings that affect SQL Performance
Chapter 12. Tips to pro-actively prevent SQL performance problems
Chapter 13. Using Collection Services data to identify jobs using system resources
Appendix A. Tools to check a performance problem

http://www.redbooks.ibm.com/abstracts/sg247326.html

Four Ways To Encrypt i5/OS Backups

2009-07-24T16:46:00.003+01:00

Joe Hertvik discusses techniques that i5/OS users have for encrypting backups for greater protection and to satisfy auditors and government agencies, explores what technologies are available, as well as the advantages and disadvantages of using each technology

You generally have four options to encrypt backup media from your i5/OS systems.
Software encryption through IBM's Backup Recovery and Media Services (BRMS) licensed program (i5/OS V6R1 only)
Software encryption through a third-party product
Hardware encryption through tape drive capabilities
Hardware encryption through an inline encryption backup solution
All of these techniques do the job but they also exact some sort of processing price on your system. In general, software-based encrypt techniques are prone to the following problems:
They force you to rewrite your backup routines to whatever commands or techniques the encryption enabling package uses. This is true whether you're using IBM's BRMS package or whether you're using a third-party package to perform the encryption.
If you're using BRMS to encrypt your data, you have to upgrade to i5/OS V6R1.
Encrypted backups don't take well to media compaction techniques, so backed up files will generally take up more space on your backup media.
Software encrypted backups generally take longer to run, because there is less compaction going on with the backup and because encryption adds another level of processing to your backup routine.

Part I focuses on software techniques

http://www.itjungle.com/fhg/fhg051309-story03.html

Part II focuses on hardward techniques

http://www.itjungle.com/fhg/fhg052009-story03.html

More Ways To Encrypt i5/OS Backups to follow...

i:ASP Data Balancer and IBM's iSeries servers

2009-07-24T16:39:00.003+01:00

IBM is continuing its push into SSDs (solid-state drives), announcing flash drives for server and storage platforms as well as new software for allocating data among different types of drives.

Enterprise SSDs allow for faster access to data but cost far more, per bit, than spinning HDDs (hard disk drives). IBM is clearly committed to the emerging technology, as are EMC and other enterprise storage vendors. IBM, though, doesn't believe SSDs will make up more than 5 percent of any average company's total storage capacity.

For the foreseeable future, SSDs will be used as part of tiered storage architectures alongside HDDs, said Charlie Andrews, director of marketing in IBM's Dynamic Infrastructure group. For that reason, the company offers a variety of software to help store "hot" data in SSDs and "cold" data on HDDs. Its latest announcement, the IBM i:ASP Data Balancer, automatically shifts different bits of data to the most appropriate tier in a storage system. The software uses an algorithm that draws upon information such as how often each bit of data has been used, Andrews said. The i:ASP Data Balancer is designed for IBM's iSeries servers, part of the company's Power
line.

From http://www.macvideo.tv/editing/news/index.cfm?newsId=116293&pagType=samechandate

Speedware reselling RPG to-.NET Code Converter

2009-05-27T09:26:00.002+01:00

Speedware is reselling and servicing Sykora-ML's ML-iMPACT code converter in the North American market. Skykor-ML claims the tool can convert 100 percent of RPG functions into fully maintainable C# or Java. That's quite unusual and special for a code converter, according to Speedware officials, who have decades of experience in the IBM midrange and mainframe migration business.

The tool converts an RPG application's DDS code to WebForms or ASP objects, while printing and other operating system-specific functions, such as batch job management, are also accounted for. What really impresses Koppe, however, is that Sykora-ML built an automated testing tool directly into ML-iMPACT, "so they can guarantee the result is exactly the same as the source platform. That, again, is very rare to see in a tool."

http://www.itjungle.com/fhs/fhs022409-story01.html

Halcyon Software growing its presence in the U.S

2009-05-27T09:18:00.001+01:00

U.K.-based Halcyon Software, a developer of systems management software for i OS and other platforms, is growing its presence in the U.S. with the goal of attracting new customers. But instead of concentrating on individual AS/400 shops, Halcyon will primarily target outsourcing firms that run large data centers, which in turn will use Halcyon's software to manage the individual clients' systems. It's a practice that has already provided successful for the software company in the U.S

http://www.itjungle.com/fhs/fhs052609-story01.html

IBM ships SSDs for Power Systems - Unix, Linux, and i5/os

2009-05-25T19:41:00.001+01:00

IBM today begins selling its first solid state disks for its Power Systems boxes, the machines it uses to attack the Unix, Linux, and OS/400 installed bases.

The IBM SSD, which comes in a 2.5-inch form factor, has about 220 MB/sec of sustained throughput on reads and about 122 MB/sec of sustained throughput on writes and can perform about 28,000 I/O operations per second (IOPS) on random transactional processing. The SSD has a 3 Gb/sec SAS interface and has an average access time of from 20 to 120 microseconds, the difference depending on where data is located on the SSD. According to IBM's specs, the SSD has about 87 times the I/O operations per second of a 15K RPM SAS drive and yet consumes about one-fifth of the power

Timothy Prickett Morgan in The Register

http://www.theregister.co.uk/2009/05/22/ibm_power_ssds/

AS400 JTOpen 6.5.1 Available

2009-05-22T13:34:00.005+01:00

Fixes and enhancements in as400 JTOpen 6.5.1 (released 2009-05-20)

- Data area: Fixed breakage in JTOpen 6.5: NoClassDefFoundError on Sun JVM's.
- Print: Fixed breakage in JTOpen 6.5: NoClassDefFoundError on Sun JVM's.
- User space: Fixed breakage in JTOpen 6.5: NoClassDefFoundError on Sun JVM's.

What is IBMs Toolbox for Java

The IBM Toolbox for Java is a set of Java classes that allow you to
access IBM i, i5/OS, or OS/400 data through a Java program. With these classes,
you can write client/server applications, applets, and servlets that work
with data on your IBM i, i5/OS, or OS/400 system. You can also run Java
applications that use the IBM Toolbox for Java on the IBM i, i5/OS, or
OS/400 Java Virtual Machine.

The Toolbox is available as an installable licensed program for the AS/400
as of OS/400 V4R2 and the iSeries as of OS/400 V5R1. Here is a breakdown of
Toolbox releases versus operating system versions:

Toolbox Installs on Connects to
release LPP release OS/400 version OS/400 version
------- -------------- -------------- --------------
V4R2 5763JC1 V3R2M0 V3R2 and up V3R2 and up
V4R3 5763JC1 V3R2M1 V3R2 and up V3R2 and up
V4R4 5769JC1 V4R2M0 V4R2 and up V4R2 and up
V4R5 5769JC1 V4R5M0 V4R3 and up V4R2 and up
V5R1 5722JC1 V5R1M0 V4R4 and up V4R3 and up
V5R2 5722JC1 V5R2M0 V4R5 and up V4R5 and up
V5R3(*) 5722JC1 V5R3M0 V5R1 and up V5R1 and up
V5R4(**) 5722JC1 V5R4M0 V5R2 and up V5R2 and up
JTOpen 1.x Not applicable Not applicable V4R3 and up
JTOpen 2.x Not applicable Not applicable V4R4 and up
JTOpen 3.x Not applicable Not applicable V4R5 and up
JTOpen 4.0-4.2 Not applicable Not applicable V4R5 and up
JTOpen 4.3-4.7 5722JC1 V5R3M0 V5R1 and up V5R1 and up
JTOpen 4.8+ 5722JC1 V5R4M0 V5R2 and up V5R2 and up
JTOpen 6.1+ 5761JC1 V6R1M0 V5R3 and up V5R3 and up

(*) Note: Toolbox release V5R3 is equivalent to JTOpen 4.3.
(**) Note: Toolbox release V5R4 is equivalent to JTOpen 4.8.

Newer versions of the Toolbox are backwards-compatible with earlier
versions. Upgrading to a newer version is usually recommended, with the one
main exception being that the Toolbox is only supported for connection
to servers running either of the two prior releases of i5/OS or OS/400.

Why Open Source?

We have chosen to make the Toolbox code open source for the following reasons:

1. To obtain new functions and features from the Toolbox user community.

2. To respond with customer and business partners requirements as rapidly
as possible.

3. To improve the ability for our customers to build and debug their own
applications when using the Toolbox functions.

4. To continue the drive to keep the IBM i platform a leader with Java technology
for application development.

Differences between JTOpen and the Toolbox LPP

1. The initial release of the source code for JTOpen used the V4R5
Toolbox codebase. That is, the Java code in the open source repository
is the same code that was used to build the V4R5 Toolbox LPP. JTOpen 2.0x
uses the V5R1 Toolbox as its codebase. The latest release of JTOpen
(JTOpen 6.x) uses the V6R1 Toolbox as its codebase.

2. When bugs are reported, fixes will be committed to JTOpen as soon as
they are realized. When applicable, these same fixes will be committed
to the Toolbox LPP and made available in a future PTF or service pack.

3. Any new functionality that is committed to JTOpen will be subsequently
added, when applicable, into the Toolbox LPP and made available in a
future PTF or service pack.

Note: All changes to JTOpen are made under the control and at the
discretion of the JTOpen Core Team. All changes to the Toolbox LPP
are made under the control and at the discretion of IBM.

4. In general, the Toolbox LPP is supported directly by IBM. JTOpen
is supported by the JTOpen user community, in which IBM participates
and contributes, specifically through developer email, the JTOpen
mailing list, and the JTOpen web forum

5. Pursuant to the IBM Public License, programmers are free to alter the
JTOpen source code and to distribute it with their own applications.

Download and installation of JTOpen

Requirements

Briefly, the requirements for using the JTOpen code are as follows:

1. A Java Virtual Machine (JVM) with a 1.2.x or higher JDK/JRE. The JTOpen
team highly recommends moving to the latest supported release of the JDK/JRE, as
maintaining backwards-compatible code with older releases becomes
increasingly difficult to support over time.

2. Almost all JTOpen functions require a TCP/IP connection to an IBM i server.

a. The server must be IBM i, i5/OS, or OS/400 V4R3 or higher.

b. The server must have the Option 12 Host Servers installed and
running. JTOpen uses the host servers as TCP/IP endpoints to
communicate with the server from a client.

c. If the Java application using JTOpen is being run directly on a server
running IBM i, i5/OS, or OS/400, then certain JTOpen functions might use
native API and/or local socket calls to improve performance.
This will only occur under certain conditions, and only if the file
jt400Native.jar is included in the application's CLASSPATH.

3. For GUI programming, either Java 2 or Swing 1.1 or higher is required.

Files

JTOpen is comprised of the following files:

Jar file Contents
-------- --------

jtopen_x_x_source.zip This is a zip file of all the source files in the repository.
It is not a Java jar file.

jtopen_x_x_javadoc.zip This is a zip file of the javadoc (in HTML format) for
the JTOpen source files. It is not a Java jar file.

jt400.jar(*) This is the main JTOpen jar file. It contains almost all open
source code (except for the few Toolbox classes that could
not be open-sourced), including the utilities package,
and the JDBC driver (JDBC 3.0).

jt400Micro.jar(*) This contains the ToolboxME (Micro Edition) classes for
use on a handheld device.

jt400Native.jar(*) Previously known as jt400Access.zip, this jar does not
contain the vaccess package. It does contain the native
optimization classes necessary for running performance-enhanced
applications on IBM i, i5/OS, or OS/400 JVM.

jt400Proxy.jar(*) This jar contains just the classes needed to run a client
application using the Toolbox proxy server. It is
especially useful in environments where a smaller jar
is needed.

jt400Servlet.jar(*) This jar contains the html and servlet packages.

jui400.jar(*) Contains the PDML runtime packages as provided by
the Graphical Toolbox.

uitools.jar(*) Contains the GUI Builder packages as provided by the
Graphical Toolbox.

util400.jar(*) Contains various utilities.

composer.jar(*) Contains XSL stylesheet composer classes.

reportwriter.jar(*) Contains XSL report processor classes.

outputwriters.jar(*) Contains PDF, PCL, and font classes.

tes.jar(*) Contains the IBM i Graphical Debugger.

jtopen_x_x_jdbc40.zip This zip file contains versions of jt400.jar and
jt400Native.jar (along with source code) that are
compatible for use with JDBC 4.0. This zip file requires
that you be running on Java 6.0 or higher.

(*) Files contained in file jtopen_x_x.zip.

There are other jar files shipped in the download for JTOpen off of the Toolbox
downloads page. Those jar files do not (yet) contain JTOpen code. They are
provided as a convenience to the developer and to mirror the objects that ship
with the Toolbox LPP.

Building and Using JTOpen

Instructions for using JTOpen:
1. Download the JTOpen jt400.jar.
2. Add it to your CLASSPATH.
3. Run your application.

Instructions for building all or part of the as400 JTOpen source code:
Note: Complete build instructions are specified in the commentary in file
/build/build.xml
1. Download the JTOpen jt400.jar.
2. Download any source files you want to change. The src.zip file includes
all of the source in the repository for convenience.
3. Set up your CLASSPATH to include everything in the correct order:
a. Your source files should be in your CLASSPATH first. Note that you
cannot point to src.zip - you must unzip it, since it contains only
source files.
b. Next, add jt400.jar.
c. Your CLASSPATH should look something like this:
CLASSPATH=C:\jt400\MyApp;C:\jt400\jt400.jar;...
4. Compile your source.
5. Run your as400 application that uses JTOpen.

The AS/400 is Dead - All Hail The 'Smart Cube'

2009-05-22T08:44:00.003+01:00

Ok, you got me, the as400 will never actually die. Its too good to die. But like Doctor Who, every few years, it changes. This time the metamorphasis of the as400 leaves us with something surprising. The 'Smart Cube'.

From IBM

The Smart Cube is a complete application-ready platform with all server hardware and software needed, pre-configured and ready-to-use, with no manuals required. In a few easy steps, businesses can be up and running with a complete IT solution to run their business, including the operating system, integrated middleware, database, security and back-office functionality such as file, print, backup and recovery, combined with the business application they acquired

(what does that sound like!)

IBM Smart Cube 7277

This product is available separately at a suggested retail price per system starting at $974.00/month or $31,128.00 and may also be included as part of a complete solution

IBM Smart Business Solution – Small Power 520 is a powerful and integrated server that is designed to run all of the business applications a medium sized business needs (e.g. Finance, Accounting, ERP, CRM, IP Telephony) with no IT complexity. The solution includes an IBM Smart Cube – Small Power 520 server with a 1-core Power 6 processor. The Smart Cube remains connected to IBM Smart Market which provides remotely delivered services including help desk and solution support, monitoring, backup and recovery, security and business collaboration. IBM Smart Cube comes with the pre-loaded IBM Smart Business Software Pack, including everything needed to run business applications and workloads. • Application Servers and Java support • Database Servers • Web Servers • File & Print Servers • Network & Application Security: • Directory Servers • Built-In backup and recovery • i Operating System. IBM Smart Cubes provide many serviceability and ease-of-use features designed to enhance the support experience for customers. IBM Smart Business Software Pack includes wizard-based application management and problem solving interfaces that can be extended to vendor application software prepared specifically for this environment. Customers will have the option to configure their solutions to automatically find and install new fixes. The Smart Desk, included in the Smart Cube, provides a single consistent interface to manage, license, administer, and maintain applications

IBM Smart Cubes come with pre-loaded IBM Smart Business Software Pack, pre-configured, ready to use; including operating system, middleware, database, security, backup and recovery and etc;

Business applications are pre-integrated with IBM Smart Business Integration Integrator and ready for automatic download at the customer installation, in simple steps.

The IBM Smart Cubes come with the pre-loaded security software, including firewall/VPN, Antivirus protection, web filtering, anti spam and application protection, to offer preemptive protection for the IT infrastructure for small and medium size companies.

The IBM Smart Support Team will provide a “single point of entry” into the larger IBM technical support structure, as well as into the software vendors’ support teams who handle the technical problems associated with application software.

The IBM Smart Cube provides a single interface and source for fix acquisition and deployment across Customer’s Smart Business solution.

The IBM Smart Cube uses powerful IBM server platforms. The IBM Smart Business customers can start with entry-level IBM Smart Cube and move to the advanced server platform, all with the compatible IBM Smart Business Software Pack.

User Space APIs

2009-05-21T19:19:00.002+01:00

User spaces are objects that used for storing user-defined information. They are permanent objects that are located in either the system domain or the user domain. They have an object type of *USRSPC and a maximum size of 16MB. You can save and restore user spaces to other systems. If, however, the user spaces contain pointers, you cannot restore the pointers even if you want to restore them to the same system.

You can use the user space APIs to:

Create user spaces to be used by list APIs to generate lists of data.
Store pointers.
Store large amounts of data. You can create a user space as large as 16 megabytes. You cannot create a data area larger than 2000 bytes.
Save information in user space objects, and save and restore the object with the information in it using CL commands.
Pass data from job to job or from system to system.

Note: If the allow user domain (QALWUSRDMN) system value contains only the QTEMP library, you can use only the user space APIs to create and manipulate user domain spaces in library QTEMP. You cannot use the Retrieve Pointer to User Space API

The user space APIs allow you to create and delete user spaces, change and retrieve the contents of user spaces, and change and retrieve information about user spaces.

For additional information, see Using User Space APIs.

The user space APIs are:

Change User Space (QUSCHGUS) changes the contents of a user space.

Change User Space Attributes (QUSCUSAT) changes the attributes of a user space object.

Create User Space (QUSCRTUS) creates a user space.

Delete User Space (QUSDLTUS) deletes user spaces created with the QUSCRTUS API.

Retrieve Pointer to User Space (QUSPTRUS) retrieves a pointer to the beginning of a user space for a high-level language (HLL) that supports pointers. HLLs that support pointers can use this pointer to manipulate the contents of a user space directly.

Retrieve User Space (QUSRTVUS) retrieves the contents of a user space. It does not retrieve descriptive information about the user space, such as its size.

Retrieve User Space Attributes (QUSRUSAT) retrieves information about creation attributes and current operational statistics of the user space, such as its size.

Sending and receiving email on i5/os - QtmmSendMail

2009-05-21T18:55:00.002+01:00

i5/os QtmmSendMail API

The i5os Send MIME Mail (QtmmSendMail) API lets you to send email from a HLL program and lets you send multiple mail attachments at one time

http://publib.boulder.ibm.com/iseries/v5r2/ic2924/index.htm?info/rzair/rzairsendmime.htm

Using the QtmmSendMail API

os400 - i5os - API Finders

2009-05-21T18:43:00.003+01:00

Use the os400 / i5os API finders to find documentation operating system APIs and some APIs for related licensed programs,by category or by name

V6R1 API Finder

V5R4 API Finder

V5R3 API Finder

Striving for Optimal Journal Performance on DB2 Universal Database for iSeries

2009-05-21T09:41:00.000+01:00

http://www.redbooks.ibm.com/abstracts/SG246286.html?Open

Journaling is an inherent feature of OS/400 on the iSeries that has been around since the early releases of the System/38. The system employs journals to ensure data integrity and recoverability and this support can further be extended to reduce the duration of an abnormal system end. Journaling also serves as the cornerstone upon which many data replication and data warehouse refresh schemes are built.
The aim of this IBM Redbook is to provide you with an understanding of the factors which influence journal performance on the iSeries and to help you identify which hardware options and software settings you can employ to minimize this impact. We will also share with you some ideas on how to minimize the impact of journaling on your iSeries from an application point of view.
We also explain the remote journal function on the OS/400, which offers a reliable and fast method to transfer journal entries to a remote iSeries server. We performed tests concerning remote journal performance and tested this function in different environments

Raz-Lees new whitepaper - Achieving PCI Compliance with IBM Power i

2009-05-21T09:23:00.002+01:00

Check out Raz-Lees new IBM i white paper - Achieving PCI Compliance with IBM Power i.

PCI-DSS consists of 12 requirements within six categories which cover best security practices. This white paper includes a summary of PCI requirements, focusing on the relevant items to Power i security. Each requirement is followed by a guideline specifying how to actually implement the requirement

http://systemisecurity.wordpress.com/2009/05/20/new-white-paper-pci-compliance-with-ibm-power-i/

as400 api - Process Commands (QCAPCMD) API

2009-05-21T09:05:00.003+01:00

The as400 Process Commands (QCAPCMD) API is used to check or run CL commands from HLLs as well as check syntax for specific source definition types

You can use the QCAPCMD as400 API to:

Check the syntax of a command string prior to running it
Prompt the command and receive the changed command string
Run a command from an HLL

An advantage of using QCAPCMD over QCMDEXC is the exception handling. An exception that occurs when using QCAPCMD command is trapped and notified via the QUSEC structure. The error is not passed up the call stack so can be handled gracefully in programs.

ILE RPG Example of QCAPCMD API

RPGLE:

fnewfile   if   e           k disk    usropn 
dcommand          s             40    inz(' ') 
dcmdlng           s             10i 0 inz(40) 
docb              ds 
d type                          10i 0 inz(0) 
d DBCSdh                         1    inz('0') 
d prompt                         1    inz('0') 
d cmdsyntax                      1    inz('0') 
d msgrtvkey                      4    inz(x'00000000') 
d reserve1                       9    inz(x'000000000000000000') 
docblength                      10i 0 inz(x'00000014') 
docbfmt                          8    inz('CPOP0100') 
dchgcmd                          1    inz(' ') 
dlngchgcmd                      10i 0 inz(0) 
dlngchgrtn                      10i 0 inz(0) 
d/COPY QSYSINC/QRPGleSRC,QUSEC 
d qused01                17    116 
c                   eval      command = 'OVRDBF NEWFILE SHARE(*YES)' 
c                   Z-ADD     116           QUSBprv 
c                   call      'QCAPCMD' 
c                   parm                    command 
c                   parm                    cmdlng 
c                   parm                    ocb 
c                   parm                    ocblength 
c                   parm                    ocbfmt 
c                   parm                    chgcmd 
c                   parm                    lngchgcmd 
c                   parm                    lngchgrtn 
c                   parm                    QUSEC 
c     QUSBavl       ifgt      0 
c     'Error on API'DSPLY 
c     qusei         dsply 
c                   end 
c                   open      newfile 
c     *loval        setll     fmt1 
c                   read      fmt1                                   30 
c     *in30         ifeq      '0' 
c     fld1          dsply 
c                   else 
c     'No Records'  dsply 
c                   end 
c                   close     newfile 
c                   eval      *INLR = '1' 

DDS for newfile: 

R FMT1                               
FLD1          10                   
FLD2          10                   
K FLD1

More as400 Command API examples to follow

AS400 API - QCMDEXC - Execute Command

2009-05-21T02:48:00.006+01:00

The Execute Command (QCMDEXC) program is an ibm as400 API that runs a single command.

The command runs as if it was not in a program. Therefore, variables cannot be used on the command because values cannot be returned by the as400 command to CL variables. Additionally, commands that can only be used in CL procedures or programs cannot be run by the QCMDEXC program. The format of the call to the QCMDEXC program is the following:

CALL PGM(QCMDEXC) PARM(command command-length)

Enter the command you want to run as a character string on the first parameter. You must specify the command library.

CALL PGM(QCMDEXC ) PARM('QSYS/CRTLIB LIB(TEST)' 22)

Remember that you must enclose the as400 command in single quotation marks if it contains blanks. The maximum length of the character string is 6000 characters; never count the delimiters (the single quotation marks ) as part of the string. The length that is specified as the second value on the PARM parameter is the length of the character string that is passed as the command. Length must be a packed decimal value of length 15 with 5 decimal positions

Example of Using QCMDEXC in an RPGLE Procedure

d Quote           C                   Const(X'7D')   
d StdCmd          S            200A                 
d StdLen          S             15P 5               

D Execute         PR                  ExtPgm('QCMDEXC')             
D     CmdStr                          Like(StdCmd)                 
D                                     Options(*VarSize)             
D                                     Const                         
D     CmdStrLen                       Like(StdLen) Const           
D*    IGCPrcCtl                  3    Options( *NoPass )           
D*                                    Const                         
*--------------------------------------------------               
d var1            S                   Like(StdCmd)                 
d var2            S                   Like(stdLen)                 
d                                     Inz(%size(var1))             

c                   eval      var1 =                               
c                             'CPYTOSTMF' + ' ' +                   
c                             'FROMMBR(' + Quote +                 
c                             '/QSYS.LIB/LIBNAME.LIB' +           
c                             '/QRPGLESRC.FILE/RPG1.MBR' +   
c                             Quote + ') ' +                       
c                             'TOSTMF(' + Quote +                   
c                             '/home/test.txt' +       
c                             Quote + ') ' +                       
c                             'STMFOPT(*REPLACE)'                 

c                   callp     Execute(var1:var2)                   

c                   eval      *inlr = *on

Another example of using QCMDEXC to execute CL commands

*                                                         
d CmdLength       s             15  5                      
d CmdString       s            256                         
 *                                                         
 * Procedure calls                                         
 *                                                         
d Command         pr                  EXTPGM('QCMDEXC')    
d  CmdString                   256                         
d  CmdLength                    15  5                      
 *                                                         
c                   eval      *inlr = *on                  
   //=========================================             
   //  *inzsr - One time run subroutine.                   
   //=========================================             
                                                           
 /free                                                     
   begsr *inzsr;
                                           
   cmdstring = 'dlyjob 10';                                
   cmdlength = %len(%trim(cmdstring));                     
   command(cmdstring : cmdlength);     
                    
   endsr;                      
 /end-free

* Procedure calls
      *
     d RUNCOMMAND      PR                  extpgm('RUNCOMMAND')
     d   CmdString                   30

     d RUNCOMMAND      PI
     d   CmdString                   30
      *
     d Command         pr                  EXTPGM('QCMDEXC')
     d  CmdString                    30
     d  CmdLength                    15  5
      *
      * Definitions
      *
     d CmdLength       s             15  5

      *
     c                   eval      *inlr = *on
        //=========================================
        //  *inzsr - One time run subroutine.
        //=========================================

      /free
        begsr *inzsr;
        cmdlength = %len(%trim(cmdstring));
        command(cmdstring : cmdlength);
        endsr;
      /end-free

QCMDEXC could also be called from CL , for instance to run a command dynamically when certain parameters that would be required are not know at run time. In this case calling QCMDEXC from a CL program would be an option. See the QCMDEXC snippet below

CHGVAR     VAR(&CMD) VALUE('CHGLIBL LIBL(' *CAT &LIBL +   
                          *TCAT ')')                                   
             CALL       PGM(QCMDEXC) PARM(&CMD &LEN)

Managed as400 hosting

More examples of Using QCMDEXC in an as400 RPGLE Procedure to follow.

Managed AS400 Hosting

2009-05-20T06:58:00.000+01:00

AS/400 & iSeries Managed Hosting

All these companies offer either management or monitoring as detailed below

iSeries Managed Hosting:
Their iSeries (AS/400) server(s) managed and located in their Data Center

iSeries Managed Collocation:
Your iSeries (AS/400) server(s) managed and located in our Data Center

iSeries Remote Monitoring & Management:
Your iSeries (AS/400) server(s) located in your Data Center, managed remotely by them

US.

Connectria offers iSeries managed hosting including managed services for AS/400, eServer & IBM System i

http://www.connectria.com/as400_hosting.asp

iseries leasing uk

More Managed as400 hosting details to follow...

IBM Announces Replacement for i5/OS

2009-05-20T01:08:00.002+01:00

Rochester MN - With the recent announcement of the new IBM Power Systems which will replace the System i hardware, the i5/OS will also be replaced and renamed. Because of the much greater capabilities of the new operating system, IBM has named it the Virtual Universe Operating System – VU/OS.

Running under VU/OS, the individual user appears to have not merely a machine of their own, but an entire universe of their own, in which they can create or remove their own programs, databases, libraries, users, networks, and planetary systems. They need only specify the universe they desire, and the VU/OS system generation program (QGOD) does the rest. This program will reside in the QSYS library. The minimum time for this function is 6 days of activity and 1 day of review. In conjunction with VU/OS, all system programs have been replaced by one program (QPROPHET) which will also reside in the QSYS library. This program has no parameters as it knows what you want to do when it is executed

From http://mid-deranged.com/2009/03/07/ibm-announces-replacement-for-i5os/

AS400 API - Retrieve Network Attributes (QWCRNETA)

2009-05-19T17:22:00.006+01:00

The Retrieve Network Attributes (QWCRNETA) as400 API lets you retrieve network attributes

Infocenter

http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/apis/qwcrneta.htm

Network Attributes

ALRBCKFP Alert backup focal point    
ALRCTLD         Alert controller    
ALRDFTFP Alert focal point    
ALRFTR         Alert filter    
ALRHLDCNT Alert hold count    
ALRLOGSTS Alert logging status    
ALRPRIFP Alert primary focal point    
ALRRQSFP Alert focal point to request    
ALRSTS         Alert status    
ALWADDCLU Allow add to cluster    
ALWANYNET Allow AnyNet support    
ALWHPRTWR Allow HPR tower support    
ALWVRTAPPN Allow virtual APPN support    
VRTAUTODEV Autocreate APPC device limit    
DDMACC         DDM request access    
DFTCNNLST Default ISDN connection list    
DFTMODE         Default mode    
DFTNETTYPE ISDN network type    
DTACPR         Data compression    
DTACPRINM Intermediate data compression    
HPRPTHTMR HPR path switch timers    
JOBACN         Job action    
LCLCPNAME Local control point    
LCLLOCNAME Local location    
LCLNETID Local network ID    
MAXINTSSN Maximum sessions    
MAXHOP         Maximum hop count    
MDMCNTRYID Modem country or region ID    
MSGQ         Message queue    
NETSERVER Server network ID    
NODETYPE APPN node type    
NWSDOMAIN Network server domain    
OUTQ         Output queue    
PNDSYSNAME Pending system name    
PCSACC         Client Access    
RAR         Addition resistance    
SYSNAME         Current system name

More as400 commands to follow

The Laughing Boardroom video...a real world example!

2009-05-19T13:34:00.004+01:00

I posted the laughing boardroom video, an old IBM ad that highlights the infrastructure and manpower changes needed when moving away from the as400 platform, as so much is simple and/or automated.

The Laughing Boardroom

Well I have actually stumbled across a real world example. John Will describes what happened when consultants convinced a utility company that they needed to move from iseries to pseries

http://www.johnmwillis.com/other/the-laughing-boardroom-ibm-eserver-iseries/

This regional, rather large, utility company had been running AS/400 for twenty years with a minimal staff. In fact the current CTO was one of the original AS/400 operators and prior to about a year ago he could have still filled in as an operator in a pinch. Other than some simple web front-ends they basically ran one production box that did all their customer care and billing services. About two years ago a team of consultants were brought in to re-deign their customer care and billing systems. The initial design took them from one production AS/400 (they called it a mainframe) to about 10 P5 physical boxes with about 50 lpars of which about 20 lpars eventually became the replacement solution. On the software side they went from a single box that basically handled everything to a very complex infrastructure

After the army of consultants had completed the project (over a year) this utility company went from 3 system administrators to about 10 system administrators and they were still understaffed. They also increased head counts for 2 system architects and a project managers. Of course at least three new managers had to be hired. All told they went from a staff of about 5 (including CTO and operations) to a staff of about 20

L3 Cache Makes All The Difference For Java Apps on IBM i

2009-05-19T08:32:00.002+01:00

Timothy Prickett Morgan is talking about the performance of the latest Power6+ system i boxes, and benchmark testing of SAP and Lawson products.

http://www.itjungle.com/tfh/tfh051809-story06.html

A couple of interesting thngs emerge...

One is that in these tests there was very little diference in performance between a 550 and a 570

A Power 520 with a single Power6+ processor with two cores running at 4.7 GHz equipped with 32 GB of memory was able to process 41,090 query navigation steps per hour on the BI-MXL test at 94 percent of CPU utilization on a data warehouse with 300 million records. (That's the smallest database used in the test, which also has 1 million and 3 million record variants.) A Power 550 with two processors and four cores activated running at 5 GHz and with 64 GB of memory was able to handle 90,635 query navigation steps per hour at 98 percent of CPU; for some reason, IBM ran the test again on this box a few weeks later and got a slightly lower 97 percent CPU utilization and only handled 90,492 query navigation steps per hour. (Go figure.) A Power 570 box with four 5 GHz cores and 96 GB of memory did slightly more work, at 93,468 query navigation steps per hour.
The message here is what I have been telling you for years: Don't buy into the Power 570 unless you have to. It is more expensive for modest workloads than a Power 550. If you don't need the expansion that the Power 570 embodies, don't do it

The other was that L3 cache is very important for java app performance

On the M3 tests, Lawson found that the initial Power 520 using that old 1.9 GHz Power5 chip could process about 75,000 invoiced order lines per hour. Moving up to the 4.2 GHz Power6 core boosted performance by 31 percent (not more than 2X as you might expect from the clock speeds because IBM radically changed the instruction pipelines with the Power6 chips), to around 98,250 invoiced order lines per hour. And while the move to the Power6+ chip only boosted the clock speed by 11.9 percent up to 4.7 GHz, the addition of the L3 cache pushed performance up 21 percent to 118,900 invoiced order lines per hour. Which makes you wonder why on Earth IBM ever cropped the L3 cache out of the boxes to artificially crimp performance on the Power 520s and the JS12 and JS22 blades in the first place. That's not a smart move if you are trying to support Java applications

PHP on the as400

2009-05-19T08:23:00.002+01:00

Timothy Prickett Morgan discusses the increasing use of PHP on System i.

http://www.itjungle.com/tfh/tfh042009-story01.html

After a year of work in the wake of the alliance, Zend and IBM started shipping a beta version of the Zend Core for i5/OS, which ran in the PASE AIX runtime environment inside i5/OS V5R4. In August of 2006, Zend Core for i5/OS became generally available and in a short time, there were thousands of downloads of the software, which IBM picked up the tab for on behalf of V5R4 shops that wanted to download a PHP engine and integrate it with their i boxes. IBM gave out statistics for downloads every couple of months, but since the creation of the Power Systems division, which converged the System i and System p lines last April, IBM has been pretty mum in terms of Zend Core for i downloads. The latest number that I have heard is that there have been 12,000 cumulative downloads of Zend Core for various i platforms, including machines running OS/400 V5R3, i5/OS V5R4, and i 6.1

According to this Gartner data, the vast majority of PHP developers in 2007 were part-time developers and hobbyists, with a small number of corporate PHP developers. But by 2013, Gartner expects there to be millions of professional PHP developers at software vendors and in IT shops, with the base of hobbyists and part-timers being about the same. And we all know who is going to be spending money on PHP tools, creating real-world, enterprise-class PHP applications, and making a living from PHP

IBM eServer iSeries - The Laughing Boardroom

2009-05-18T19:17:00.000+01:00

Came across this....funny

Web 2.0 with AS/400 - How To Use ERP To Create Useful Services For Customers

2009-05-18T18:58:00.000+01:00

Web 2.0 with AS/400

View more presentations from Francesco Fullone.

Building Dynamic Web Applications on i5 with PHP

2009-05-18T18:56:00.000+01:00

Building Dynamic Web Applications on i5 with PHP

View more presentations from John Coggeshall.

Integrating PHP With System-i using Web Services

2009-05-18T18:55:00.000+01:00

Integrating PHP With System-i using Web Services

View more presentations from Ivo Jansch.

Adapt, Survive and Thrive with as400 - Eight Pillars of an Enterprise Application Architecture

2009-05-18T18:53:00.000+01:00

Eight Pillars of an Enterprise Application Architecture

View more presentations from Martin Fincham.

Your iSeries is a jewel...but what about the software?

2009-05-18T18:48:00.000+01:00

Your iSeries is a jewel...but what about the software?

View more presentations from Martin Fincham.

Linoma Crypto Complete - Encryption Suite for System i

2009-05-18T18:46:00.000+01:00

Linoma CryptoComplete

View more presentations from Stuart Marsh.

AS400 OS400 API Include Files

2009-05-18T17:59:00.002+01:00

The system include or API copybook library QSYSINC, contains all the source includes for APIs shipped with OS/400 (i5/os). This optional library is fully supported, so any errors found in the includes can be reported to IBM.

http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/apis/conQSYSINC.htm

Decrypt Data on AS400 - QC3DECDT, Qc3DecryptData API

2009-05-18T17:37:00.003+01:00

The Decrypt Data (OPM, QC3DECDT; ILE, Qc3DecryptData) API restores encrypted data to a clear (intelligible) form

example

calling Qc3EncryptData with Pointers

http://forums.systeminetwork.com/isnetforums/showthread.php?p=211649

Sample program to demonstrate use of Cryptographic Services APIs.
APIs demonstrated in this program are:
Create Algorithm Context
Create Key Context
Decrypt Data
Destroy Key Context
Destroy Algorithm Context

http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/apis/qc3BillCusILERPG.htm

as400 database connection strings

2009-05-18T15:40:00.003+01:00

Connection string examples when connecting to an as400, iseries, system i, os400, i5os

as400 JDBC connection string

jdbc:as400://mySystem;user=myUid;password=myPwd;

IBM DB2 for i .NET data provider

DataSource=myServerAddress;UserID=myUsername;Password=myPassword; DataCompression=True;

IBM Client Access OLE DB provider

Provider=IBMDA400;Data Source=MY_SYSTEM_NAME;User Id=myUsername;Password=myPassword;

.NET Framework Data Provider for OLE DB

Provider=IBMDA400;Data Source=MY_SYSTEM_NAME;User Id=myUsername;Password=myPassword;

Client Access ODBC driver

Driver={Client Access ODBC Driver (32-bit)};System=my_system_name;Uid=myUsername;Pwd=myPassword

iSeries Access ODBC driver

Driver={iSeries Access ODBC Driver};System=my_system_name;Uid=myUsername;Pwd=myPassword;

.NET Framework Data Provider for ODBC

Driver={Client Access ODBC Driver (32-bit)};System=my_system_name;Uid=myUsername;Pwd=myPassword;

More as400 database connection strings to follow

80 Column Punched Cards and the History of RPG on the AS400

2009-05-18T14:57:00.003+01:00

An article where Jon Paris discusses the lineage of punched cards that leads to RPG and the as400...

http://ibmsystemsmag.blogs.com/idevelop/2007/09/of-80-column-pu.html

Anyway it got me thinking about how little many of us know of our own history as it relates to the IT industry. Would you believe that there are people out there who actually believe that Bill Gates and Microsoft invented the concept of a windowing GUI! They probably believe they invented DOS too--poor misguided souls.

On the subject of punch cards, let's take a quick look at how they impacted our favorite language--RPG. Since some of you may not have actually seen a punch card before, here's a picture of one so that we all know of which we speak:

As you can see there are 80 vertical columns, which explains the 80-column limit in RPG II and RPG III. You might also have wondered why the first five columns of the spec are designated as the sequence number. Well, suppose you had a 600-line RPG program and it was on punch cards. Now suppose that you dropped the box and 600 cards hit the floor. How long do you think it would take you to put the program back in order? Now you understand the reason for the sequence number.

IBM Redbooks | IBM i5/OS Program Conversion: Getting Ready for i5/OS V6R1

2009-05-18T13:51:00.002+01:00

http://www.redbooks.ibm.com/Redbooks.nsf/RedbookAbstracts/redp4293.html?Open

This IBM Redbooks Redpaper publication is intended for i5 system administrators and field technicians to help them understand and prepare for upgrading or migrating to i5/OS V6R1. It explains what the program conversion is and why programs are being created or re-created on V6R1. It then provides detailed steps for using the ANZOBJCVN tool on V5R3 or V5R4 to prepare for V6R1 object conversions. Finally this Redbooks Redpaper discusses the program conversion methods for converting programs to run on i5/os V6R1

Redbook - as400 Security - IBM System i Security: Protecting i5/OS Data with Encryption

2009-05-18T13:46:00.002+01:00

Redbook - as400 Security - IBM System i Security: Protecting i5/OS Data with Encryption

http://www.redbooks.ibm.com/abstracts/sg247399.html

Part 1, "Introduction to data encryption" , introduces key concepts, terminology, algorithms, and key management.

Part 2, "Planning for data encryption" , provides critical information for planning a data encryption project on i5/OS.

Part 3, "Implementation of data encryption" , provides various implementation scenarios with a step-by-step guide

Part 1. Introduction to data encryption
Chapter 1. Data encryption: the big picture
Chapter 2. Algorithms, operations, and System i implementations
Chapter 3. Key management concepts

Part 2. Planning for data encryption
Chapter 4. Analyzing needs and defining scope
Chapter 5. Managing keys on System i
Chapter 6. Choosing a data encryption method
Chapter 7. Database considerations
Chapter 8. Application considerations
Chapter 9. Backup considerations

Part 3. Implementation of data encryption
Chapter 10. SQL method
Chapter 11. Cryptographic Services APIs method
Chapter 12. HW-based method

Encrypt Data on as400 (QC3ENCDT, Qc3EncryptData)

2009-05-18T13:28:00.004+01:00

Encrypt Data on as400 (QC3ENCDT, Qc3EncryptData)

The Encrypt Data API protects data privacy by scrambling clear data into an unintelligible form, OPM, QC3ENCDT; ILE, Qc3EncryptData

http://publib.boulder.ibm.com/iseries/v5r2/ic2924/index.htm?info/apis/qc3encdt.htm

Simplified RC4 or AES Encryption by Bob Cozzi

In the last issue, I reported on a few of the new OS/400 encryption APIs: Qc3CalculateHash, Qc3EncryptData, and Qc3DecryptData.
Calling one of these APIs requires careful interpretation of the API's parameter list. The parameter lists consist of various data structures and formatting codes that can be somewhat vexing to say the least. Unless it's for performance reasons, I can't understand why IBM continues to publish APIs that require such complex parameters. Even I find them confusing, and I've been working with OS/400 APIs since before the first ones were even announced.
To help simplify matters, I've written two subprocedures that accept data as input (along with the encryption key/password) and return the data encrypted or decrypted, depending on which subprocedure you call

http://www.mcpressonline.com/security/i5/os/simplified-rc4-or-aes-encryption.html

APIs by Example: AES Encryption to Actual Field Length

By: Carsten Flensburg

I've discussed and demonstrated the Cryptographic Services APIs in past issues of this newsletter. The encryption examples that I presented have all used the Advanced Encryption Standard (AES) algorithm, which offers a current, strong, and well-performing encryption method that has been adopted as an encryption standard by the U.S. government. If you have followed those examples, you know that AES encryption is a block cipher and that the ciphertext produced by AES therefore always is an exact multiple of the block size applied to the cryptographic process. The block size specified for the AES algorithm is 16 bytes, although the Cryptographic Services APIs' implementation of AES offers 24 and 32 bytes block sizes as well.

For some purposes and situations, the block-size determined length of the ciphertext could be regarded as an inconvenience. In today's APIs by Example, I explain a method for handling data not a multiple of the block length

http://systeminetwork.com/article/apis-example-aes-encryption-actual-field-length

More Encrypting Data on as400 to follow...

Using os400s QEZSNDMSG to send messages to users

2009-05-17T17:52:00.000+01:00

The os400 QEZSNDMG API allows you to send a message to users and even allows you to throw up the Send a Message screen

Example

http://archive.midrange.com/rpg400-l/200512/msg00006.html

Getting a dump of the iseries 5250 Data Stream Commands

2009-05-11T23:33:00.003+01:00

Dumping the Iseries 5250 Data Stream

To dump the dynamic screen manager APIS ( DSM ) 5250 data stream commands:

Create a physical file somewhere in your library list called QSNDEBUG with record length 2000.
DSM will dump 5250 data stream commands to QSNDEBUGF found in the library list

Using as400 QRCVDTAQ api to retrieve a message / entry from a dataqueue

2009-05-11T09:37:00.003+01:00

Heres an example of using the QRCVDTAQ as400 api to retrieve a message / entry from a as400 dataqueue

C                     CALL 'QRCVDTAQ' 
C                     PARM 'MYQUEUE' DTQ    10 
C                     PARM 'QTEMP'   DTLIB  10 
C                     PARM 100       LENGTH  50 
C                     PARM           DATA 
C                     PARM 0         WAITT   50 
C                     PARM           ORDER   2 
C                     PARM           KLEN    30 
C                     PARM           KEY 
C                     PARM           SNDLEN  30 
C                     PARM           ID

DTQ as400 Data queue name
DTLIB as400 library name
LENGTH Length of entry received.
zero if no entry received.
DATA Entry received. Must be minimum length indicated by LENGTH at least.
WAITT Time in seconds to wait for an entry.
Zero = no wait.
-ve number = wait until entry received.

(only used if dataqueue keyed, optional)

ORDER Condition operator, EQ, NE, LT, LE, GT or GE.
KEYLEN Key length
KEY Key value. Length indicated by KEYLEN.
SNDLEN Length of SENDER field
SENDER Field to receive sender ID. Usually 44 bytes

Using as400 QRCVDTAQ api to retrieve a message / entry from a dataqueue

Using as400 QSNDDTAQ api to put a message / entry on a dataqueue

2009-05-11T09:24:00.005+01:00

Heres an example of using the as400 QSNDDTAQ api to put an entry on a data queue

C                     CALL 'QSNDDTAQ' 
C                     PARM 'MYQUEUE' DTQ     10 
C                     PARM '*LIBL'   DTLIB   10 
C                     PARM 10        LENGTH  50 
C                     PARM 'START'   DATA 
C                     PARM 4         KEYLEN  30 
C                     PARM '*CMD'    KEY

API Parameters

DTQ         as400 Data queue name 
DTLIB       as400 library name (or *LIBL to search library list) 
LENGTH      Entry length 
DATA:       Entry.  Maximum length indicated by LENGTH. 
KEYLEN:     (optional, only required if if dataqueue *KEYED) Key length 
KEY:        (optional, only required if if dataqueue *KEYED)  Key value 
maximum length indicated by KEYLEN.

as400 jobs

More info on using Using as400 QSNDDTAQ api to put a message / entry on a dataqueue to follow...

AS400 Jobs: Do you have a job at the moment?

2009-05-11T00:00:00.005+01:00

AS400 Jobs question

Do you have an as400 job at the moment

The reason for me asking this question is because at the moment I dont have an as400 job. Plus I came across this old as400 related jobs article on IT Knowledge Exchange asking the very similar question. They mention that it may be down the fact that its difficult looking for work on a system that is round about 20 years old, which the as400 is now.

http://itknowledgeexchange.techtarget.com/iseries/as400-jobs-are-you-looking-for-work/

Plus companies are modernising their so-called 'legacy' as400 systems based on RPG to new and shiney windows and linux systems using java or .Net.

So with that in mind, and the ever present now, credit crunch, it would appear that the job market for technicians with as400 skills maybe getting smaller and smaller. Although to balance that there are still a lot of companies that rely on their as400 for their business processes to run, almost without hiccup Given that, I still think we will see as400 jobs around for some time yet

as400 LPAR CPU statistics and documentation tool for IBM Power systems servers

2009-05-09T21:51:00.003+01:00

This tool produces historical CPU graphs of as400 LPAR's and shared CPU usage, physical and logical config of managed systems/LPAR's and any changes in state and configuration

http://www.ibm.com/developerworks/wikis/display/virtualization/lpar2rrd%20tool

More as400 LPAR information to follow

Free AS400 & iSeries Software Tools & Utilities Downloads

2009-05-09T21:44:00.008+01:00

Lots of free AS400 and Iseries Tools and Utilities

LPAR CPU statistics and documentation tool for IBM Power systems servers

Change Current User

This will allow you to change the current user that you are logged on with without logging off the as400 system first. This command uses the QSYGETPH API to verify the password entered and then uses the QWTSETP API to actually change the user that is currently signed on. This is very useful in making sure that a peticular program is always run as a certain user

Change Current User

Calculate Dates

Calculate dates using RPG IV date fields. This is useful in determining the effect of different calculations on date fields. It will prompt you to enter a date and allow you to try different scenarios and see the results

Calculate Dates

More as400 tools and utilities to follow

The performance difference between a true SQL index on the as400 and a keyed logical index

2009-05-09T09:46:00.005+01:00

Apparently there is a huge performance difference on the as400, that has existed since V4R2, between SQL indexes and DDS created logical files. The performance is so much better that it is worth converting all DDS logicals to SQL, even if they are only used by RPG programs

The evolution of the as400 / iSeries / i5 has resulted in a mix of old and new technologies. Most notably
are the methods used to create, populate and manipulate databases. Many iSeries/i5 application
developers have embraced modern tools for creating front end masterpieces to their existing data;
however the underlying foundation, the database itself, has been woefully neglected. Basically
the existing databases were created using a tool known as DDS (Data Description Specification).
All other Relational Database Management Systems (RDMS) use Structured Query Language, or
SQL, to define the database.
For many iSeries/i5 developers initial attempts in the use of SQL have resulted in unacceptable
performance causing system administrators and/or Chief Information Officers to discourage its
use. For others, the ease of use of SQL has made it the preferred tool for data creation and access.
When these two groups come together the result is like a bad beer commercial. Shouts of “It’s
great!” are hurled in response to yells of “Less fulfilling!”
As IBM continues to enhance DB2 UDB for iSeries (e.g. the new and improved SQL Query
Engine, more efficient data access methods, new database primitives, etc) the decision to use
SQL over traditional methods will no longer be if, but when. In fact, many iSeries/i5 shops are
developing all new applications using SQL. In addition, the use of SQL defined databases may
result in improved throughput as a result in changes to the underlying architecture (more on this
later).
So all new SQL development will benefit from new database technology but what about the
existing DDS defined databases that are still serving thousands of applications using Record
Level Access (RLA) methods via High Level Language (HLL) read and write operations? Is there
a way that these applications can take advantage of SQL database enhancements without a total
rewrite?
The answer is a resounding Yes! This is the basic premise of this article. In essence this article
provides a high level overview of the madness behind the methods known as the Stage 1 DDS to
DDL reengineering strategy detailed in the soon to be released Redbook "Modernizing iSeries
Application Data Access - a Roadmap Cornerstone".

Full PDF here -
as400 DDS and SQL Performance

Good luck with your as400 logical file performance

Used as400s

2009-05-08T15:56:00.004+01:00

A list of vendors of Used AS400s

US.

ISM - Used Iseries AS400, Custom build AS400 i5 servers parts Big inventory International dealer

http://www.ismweb.com/

XCC - Used IBM iSeries AS400, AS/400, AS 400 Server, Refurbished, New, Lease, IBM AS400 iSeries Dealer Resller

www.xcc.com/ibm/as400_iSeries.lasso

as400dealer - New and Used IBM i5 Servers (AS/400) - Used iSeries Servers · Used AS400 Servers · Refurbished iSeries Servers · Refurbished AS400 Servers

http://www.as400dealer.com/

Vibrant - Vibrant stocks a vast inventory of used and refurbished AS/400 servers, configuration, upgrades, peripherals and parts

www.vibrant.com/ibm-iseries/used-as400.php

Abacus - Used AS/400 and Used iSeries Servers

www.abacusllc.com/products/servers-ibm-iseries.asp

Penn Computer - Used IBM iSeries | Buy, Sell, Lease Rent

www.penncomputer.com/IBMiSeries/default.htm

Spectra - Used iSeries, used system i5 and used AS400 servers. 520, 550, 570, 595, 800, 700 and 600 Series

www.spectra.com/usedsystems/ibm/4/iseries.htm

Midand Info - New/Used iSeries Hardware, iSeries Systems, Upgrades
Parts, Software & Prof. Service

www.midlandinfosys.net

UK.

SupaPrice - Used As 400 Sale, Save big on Used As 400.
Used As 400 up to 62% off!

SupaPrice.co.uk/Used+As+400

Weycomms - IT Hardware Traders, Used IBM i-Series, p-Series
& x-Series Hardware

www.weycomms.co.uk

Covenco - Iseries and System i, Power6 to legacy systems. Servers, disk, memory, in stock immed. ship

http://www.covenco.co.uk

Bluechip - iSeries & AS400 Systems, IBM iSeries Hardware Upgrades & Sales from IBM Midrange Specialists

http://www.bluechip.co.uk

What is QZHQSSRV job?

2009-05-07T21:05:00.003+01:00

On the as400, QZHQSSRV is one of the prestart jobs that will be running in the QUSRWRK subsystem.

A prestart job is a batch job and will run on the server before a program on a remote system tries to connect with that server. Usually multiple prestart jobs of a particular type are configured to run. Prestart jobs are run to increase performance of initiations and connections to a server. Host server functions, that use prestart job, use the sockets communications interface support

The host servers are:

Network print server
Remote command and distributed program call server
Central server
Database server
Secure database server
File server
Secure file server
Data queue server
Signon server

These are the programs called when the prestart job is started for host server.

Network Print QSYS/QNPSERVS
Remote command and program call QSYS/QZRCSRVS
Central QSYS/QZSCSRVS
Database QSYS/QZDASOINIT
Secure Database QSYS/QZDASSINIT
File QSYS/QPWFSERVSO
Secure File QSYS/QPWFSERVSS
Data Queue QSYS/QZHQSSRV
Signon QSYS/QZSOSIGN

The prestart jobs usually take the name of the program that they call, so QZHQSSRV is a prestart job for a remote system to communicate with a data queue on the server.

About Me

2009-05-07T12:37:00.006+01:00

Hi,

Im Colin Williams, the 'Webmaster' of this blog. Im an as400 IT consultant (currently on a career break, not my choice, blame the credit crunch!) with 20 years experience of many aspects of as400 systems and development. Im based near London, but will work anywhere in the world if an obscene amount of money is offered (seriously)

If you have any comments on this blog, or any suggestions, need an experienced as400 guy, or just need some counselling (apparently im a good listener), drop me an email...

colinwilliams007 at yahoo.co.uk (antispam, you know what to do!)

System i | AS400 | Iseries Business Partners

2009-05-07T02:59:00.002+01:00

System i | AS400 | Iseries modernization solutions

http://www.bcdsoftware.com

IBM System i Developer Road Atlas

2009-05-07T02:50:00.001+01:00

The System i Developer Road Atlas illustrates all the possibilities for development activities; including modernization, new development and the inclusion of components which have already been created. The Road Atlas shows key activities required for developers from seemingly diverse backgrounds as RPG, Java and PHP to integrate components together creating on demand applications

http://www-03.ibm.com/systems/i/resources/roadmap/

Websphere Application Server for Iseries

2009-05-07T02:37:00.001+01:00

Version 7.0 is the latest release WebSphere Application Server on iseries and is supported on IBM i.

http://www-03.ibm.com/systems/i/software/websphere/index.html

Using the .Net toolset to develop desktop and Web-based applications for IBM i

2009-05-06T16:11:00.004+01:00

Richard Schoen discusses using .Net to develop IBM i apps...

With a little education on how to use a technology like .NET to develop applications, a System i programmer can quickly write a graphical application on top of an existing System i solution. This adds a new user interface to important parts of an existing system or simply offers ease of access to existing ERP data from a Windows or Web-based inquiry

http://www.ibmsystemsmag.com/ibmi/october07/trends/17571p1.aspx

IBM is abandoning storage....

2009-05-06T15:18:00.004+01:00

or at least they are not taking it seriously, according to this article by storage analyst Barry Burke...

In my book, when you trivialize the importance of ANY technology to the point of having your supplier announce GA and availability rather than doing it yourself, it means something. And when IBM's sales force is to this day telling prospects that flash SSDs are "unproven technology" and "not ready for the enterprise," I can only conclude that IBM is embarrassed to admit some huge limitation or inadequacy of their products when used with Flash

...the aging, decrepit DS8K is no longer a viable storage platform for the enterprise. Later this year, IBM will finally get around to upgrading the aging DS8K processors to the p6, but it won't be enough to catch up with the Symmetrix V-Max

http://thestorageanarchist.typepad.com/weblog/2009/05/2001-ibms-amazing-splash-dance-part-deux.html

LANSA beefs up as400 application modernistation options with aquisition of aXes

2009-05-06T15:08:00.005+01:00

Lansa has purchased aXes as400 modernisation suite of products. The products are

aXes Terminal Server provides Web enablement of 5250 applications with the automatic generation of a highly customizable graphical user interface (GUI).

aXes Data Explorer Server provides an easy way to extract and then publish live DB2/400 data in a browser or to send query output to desktop applications like Microsoft Word and Excel.

aXes Spool File Server provides point-and-click access to output queues and spool files, with print-ready documents available in PDF, XML, HTML, or text formats

http://www.axeslive.com/home.php

Aldon Introduces a new Build and Release Management Product to IBM i

2009-05-06T15:01:00.002+01:00

While version control tools give you the ability to manage software versioning through check-outs and check-ins, it can’t help you with the software build and release process. Aldon’s Build Release Management solution gives you total control of the entire build release management process by taking advantage of the benefits that an application lifecycle management offering brings

http://www.aldon.com/sol/brm/ov/

Get Time to the Millisecond in ILE C on as400

2009-05-06T14:33:00.002+01:00

Show examples of manipulating dates and time from ILE C using APIs CEELOCT for current time and CEEDATM for date time or timestamp formatting on as400

http://systeminetwork.com/article/get-time-millisecond-ile-c

5250 Emulators

2009-05-06T08:54:00.004+01:00

For easy access to IBM AS/400 (System i, iSeries) sessions, try one of these 5250 terminal emulators

LINUX 5250 Emulators

Mocha Linux TN5250 (Shareware) MochaSoft

http://www.mochasoft.dk/linux.html#tn5250.