Managing IFS Objects with TURNOVER

Lesson Objectives

By the end of this lesson, you will be able to:

  • Understand how TURNOVER® for iSeries (now Lifecycle Manager) manages Integrated File System (IFS) objects, including stream files, directories, and non-native source.
  • Configure application definitions and type codes to support IFS objects for checkout, promotion, and distribution.
  • Use Programmer Worklist Manager (PWM) and forms to handle IFS changes, including editing with RDi and compiling.
  • Implement advanced features like exits, APIs, and integrations for custom IFS workflows.
  • Troubleshoot IFS-related issues and apply best practices for auditing and multi-platform alignment.

This summary distills the 63-page guide (likely pre-2018 edition, titled "for iSeries") into practical modules for developers and administrators. It focuses on extending TURNOVER®'s change management to IFS for unified control over native and non-native objects. Note: A related 2021 white paper, "Coding with Source Stream Files for Integrated Enterprise Software Management," provides updated insights on IFS management with TURNOVER® Lifecycle Manager, including support for stream files in repositories like SVN or Git; check UNICOM/SoftLanding for the latest guide or Release 2.100+ updates.

Key Concepts

  • IFS Objects: Stream files (e.g., source code in text format), directories, and non-IBM i files; managed alongside native objects for enterprise integration.
  • App Definitions: Extend to IFS type codes (e.g., *STMF for stream files); define methods for checkout, promotion, distribution.
  • PWM and Forms: Add/edit IFS items; promote with custom commands (e.g., CPY for copies).
  • Editing/Compiling: Use RDi for stream files; compile with SRCSTMF parameter (IBM i 7.1+ enhancements).
  • Integrations: Exits/APIs for custom logic; support for repositories (e.g., SVN via Supplement #66).
  • Prerequisites: TURNOVER® v5.4+; RDi or similar for editing; configured cross-references.

Module 1: Introduction to Managing IFS Objects

Overview

  • IFS extends IBM i filesystem for hierarchical storage (/root, /QOpenSys, etc.); enables multi-platform dev.
  • TURNOVER® treats IFS objects as first-class: Checkout/reserve paths, promote/distribute with forms.
  • Benefits: Unified change control, auditing, versioning for Java/PC/Web/UNIX source alongside IBM i.

IFS Structure in TURNOVER®

  • Stream Files: Text-based source (e.g., RPG in /myapp/src/program.rpg).
  • Directories: Managed as *DIR types.
  • Non-Native: Handle via custom type codes (e.g., *JAVA, *HTML).

Module 2: Configuring for IFS Objects

Application Definitions

  • TURNOVER 1 > Work with Apps > Add IFS types: *STMF (stream file), *DIR (directory).
  • Methods: Promote with CPYFRMSTMF/CPYTOSTMF; distribute via *FTP overrides.
  • Levels: Specify IFS paths as "libraries" (e.g., /dev/src to /prod/src).
  • Type Codes: Define create/promote (e.g., for *STMF, use CRTSTMF or copy).

Global Defaults and Overrides

  • Enable IFS: Utilities > Global Defaults > IFS flags (e.g., archive stream files).
  • Remotes: Set *IFSFTP for distributions (Supplement #26).
  • Compiling: Use SRCSTMF on commands (e.g., CRTBNDRPG SRCSTMF('/path/file.rpg')).

Integrations

  • RDi: Edit stream files; integrate with TURNOVER® Client for checkouts.
  • Repositories: SVN/Git for versioned storage (2021 white paper emphasizes this).

Module 3: Managing IFS in PWM and Forms

Adding/Checkout in PWM

  • STRPWM > F6 Add Item: Specify *STMF type, path (e.g., /myapp/file.txt).
  • Option 21: Checkout reserves path; copies to dev area.
  • Editing: Use RDi or EDTF; Option 32 for stream file edit.

Building Forms

  • Option 46: Add IFS to form; sequence after dependencies.
  • Edit (42): Add pre/post commands (e.g., CHGOWN for authorities).
  • Promotion: Copies/moves files; handles directories recursively.

Compiling from IFS

  • For source stream files: Compile to objects (e.g., programs from .rpg files).
  • Limitations: OPM may need temp member conversion; ILE supports directly (IBM i 7.4+ for CLLE).

Module 4: Promotion, Distribution, and Auditing

Promotion Rules

  • Levels: Promote from dev to test/prod paths.
  • Data Handling: For directories, optional recurse; preserve attributes.

Distribution to Remotes

  • Use *IFSFTP: Send stream files via FTP; configure overrides for paths.
  • Hub/Production: Receive and install IFS changes.

Auditing and History

  • Archive: Store versions in ARCHIVESRC or IFS paths.
  • Reports: Include IFS in object history (Option 4), form status.

Module 5: Advanced Features and Troubleshooting

Exits and APIs

  • IFS Exits (F8 on Work with Exits): Custom for pre/post-checkout, promotion (e.g., EXIT for stream file validation).
  • APIs: Commands like ADDPWLITM support IFS paths.

Troubleshooting

  • Path Issues: Ensure /QSYS.LIB mapping; check authorities.
  • Compile Errors: Verify SRCSTMF support; use logs.
  • Distributions: Monitor FTP logs (TOFTPLOG); handle partial failures.

Best Practices

  • Start Small: Pilot with new projects.
  • Repos: Use SVN/Git for versioning; TURNOVER® audits changes.
  • Modernize: Convert native source to IFS for enterprise tools.

Assessment and Next Steps

  • Quiz Ideas: How to add an IFS stream file to PWM? Compile command for IFS source? Benefits of IFS in TURNOVER®?
  • Practice: Configure an app for *STMF, checkout/edit a stream file, promote via form.
  • Further Learning: User Guide (v101) for forms/PWM; Administrator’s Guide (Release 2.100) for defs; Supplements #30 (Exits/APIs), #26 (Direct FTP). The 2021 white paper expands on stream files and repos. Contact UNICOM support (tech.support@unicomsi.com or +1-603-924-8818) for 2025 updates or RDi integrations

Resources

Resource 1

Managing IFS Objects with TURNOVER

 Download
Open
Done?
 Mark lesson complete
Previous Lesson
Next Lesson
{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}
>