Lesson Objectives
By the end of this lesson, you will be able to:
- Understand the concept of Independent ASPs (iASPs) on IBM i and their differences from regular ASPs.
- Configure TURNOVER® Lifecycle Manager (Release 5.3+) to promote objects into iASPs, respecting its limitations.
- Set up job descriptions and manage ASP groups to ensure successful promotions.
- Apply default library settings for archiving objects in iASPs.
This summary condenses the 3-page supplement (Version 100, January 2010) into a concise guide for administrators. iASPs, introduced with IBM i V5R2M0, allow independent disk unit management, and this supplement outlines TURNOVER®'s support for promoting objects into them. Note: As of October 24, 2025, this is the latest version based on available data; check softlanding.com for updates.
Key Concepts
- iASPs vs. Regular ASPs: iASPs (17-32) allow duplicate library names across ASP groups, managed by the SETASPGRP command, unlike ASPs 1-16.
- TURNOVER® Limitations: Partial iASP support requires manual ASP group management and restricts cross-group promotions/explosions.
- Job Descriptions: Critical for setting initial ASP groups (INLASPGRP parameter) during form runs.
- Archiving: Uses specific library naming conventions (e.g., Tform#DH, Rform#xx) for iASP objects.
- Prerequisites: IBM i V5R2M0+, TURNOVER® Release 5.3+, and user responsibility for ASP group consistency.
Module 1: Understanding iASPs and TURNOVER® Support
What Are iASPs?
- Introduced in V5R2M0, iASPs (17-32) allow offline/online disk units independently.
- SETASPGRP command specifies the active ASP group; libraries can duplicate names across groups.
TURNOVER® iASP Support
- Since Release 5.3 (October 2004), supports promoting objects into iASPs with limitations:
- User must set ASP group (via SETASPGRP or INLASPGRP).
- No cross-ASP group promotions or explosions.
- All form-related libraries must be in the same ASP group or user ASPs.
- Cross-reference, history, and auditing don’t track ASP groups.
Important Notes
- Read supplement fully before proceeding.
- TURNOVER® libraries (e.g., SOFTTURN) should not be in iASPs.
- Avoid SETASPGRP in pre/post commands or exit points; use job descriptions or form pre-run exits.
Module 2: Configuring Promotions into iASPs
Requirements and Responsibilities
- Ensure ASP group is set before work (SETASPGRP or INLASPGRP in job description).
- Maintain consistency: No mid-job ASP group changes.
- Set ASP group before recovery form creation or error checks.
Job Description Setup
- Since Release 5.3, these jobs use INLASPGRP(*JOBD):
- Form Run (Tform#G)
- Form Finalization (Tform#F)
- Form Receive (TOAUTORCV)
- Use form header job description (except receive, which uses TURNOVER job description).
- For other processes (default INLASPGRP(*CURRENT)), manually set via SETASPGRP or custom job description.
Promotion Considerations
- Libraries (library list, target/from libs, job description lib) must be in the same ASP group.
- Receiving forms may need correct initial ASP group.
- Exploding to 485+ libraries: Base object cannot be in ASPs 17-32.
Module 3: Default Settings for iASP Promotions
Archive Libraries
- ASPs 17-32: Tform#DH through Tform#DW.
- iASPs: Rform#xx (where 'R' is from TARCHPRE data area, 'xx' is base 36 number).
- TARCHPRE default is 'R'; change to another letter (not A, Q, T, W, X, Z) if needed.
Troubleshooting
- Avoid archiving offline forms across ASP groups.
- Monitor for “Changed outside of TurnOver” messages due to duplicate library names.
Assessment and Next Steps
- Quiz Ideas: What’s the difference between iASPs and regular ASPs? How to set ASP group for a form run? Limitations of cross-ASP promotions?
- Practice: In a test IBM i with iASPs, set up a job description with INLASPGRP, create a form, and promote an object into an iASP.
- Further Learning: Refer to the Administrator’s Guide (TN4A-2100-02); contact SoftLanding Technical Support (techsupport@softlanding.com, +1-603-924-8818) for assistance. Explore iASP configurations with current TURNOVER® releases (e.g., 2.100 as of 2022).