Run any Skill in Manus with one click

migrate-while-active

Stars3

Forks1

UpdatedMarch 16, 2026 at 02:34

Monitor IBM i Migrate While Active environments including migration manager state, library and IFS object tracking, migrated objects, compression factors, synchronization estimates, and network bandwidth. Use when user asks about: (1) migration status or progress, (2) library or IFS objects being migrated, (3) migration failures or errors, (4) completed migrations, (5) data compression ratios, (6) final synchronization time estimates, (7) migration network bandwidth, or (8) cutover planning.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ajshedivy

ajshedivy/ibmi-agent-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

File Explorer

4 files

SKILL.md

readonly

name

migrate-while-active

description

IBM i Migrate While Active Monitoring

Monitor Migrate While Active environments including migration manager state, library and IFS tracking, compression, and synchronization estimates using QSYS2 SQL services.

Available Tools

The ibmi CLI is the primary tool for migration monitoring. Set SKILL_DIR to this skill's installed location (the directory containing this SKILL.md file):

# SKILL_DIR = directory containing this SKILL.md
# Examples: ./skills/migrate-while-active, ~/.claude/skills/migrate-while-active

ibmi tools --tools "$SKILL_DIR/tools/" --toolset migrate_while_active_default
ibmi tool get_migration_manager_info --tools "$SKILL_DIR/tools/"
ibmi sql "SELECT * FROM QSYS2.MIGRATION_MANAGER_INFO"

Service Selection Guide

Migration Status

QSYS2.MIGRATION_MANAGER_INFO -- Overall migration state, phase, and node info
QSYS2.LIBRARY_MIGRATION_LIST -- Library objects being tracked for migration
QSYS2.IFS_MIGRATION_LIST -- IFS objects being tracked for migration

Completed Migrations

QSYS2.MIGRATED_LIBRARY -- Successfully migrated library objects
QSYS2.MIGRATED_IFS -- Successfully migrated IFS objects

Planning & Estimation

SYSIBMADM.DATA_COMPRESSION_FACTOR -- Compression ratios for data types
QSYS2.ESTIMATE_FINAL_SYNCHRONIZATION_TIME -- Final sync time estimate
QSYS2.MIGRATION_NETWORK_BANDWIDTH -- Network bandwidth measurements

Key Capabilities

Migration Tracking

Manager Status -- Current migration phase, stage, and node states
Library Migration -- Track library-based object migration progress
IFS Migration -- Track IFS object migration progress
Failure Detection -- Identify objects that failed to migrate

Completion Monitoring

Migrated Libraries -- Verify library objects completed migration
Migrated IFS -- Verify IFS objects completed migration
Time-based Filtering -- Show objects migrated within recent hours

Cutover Planning

Compression Analysis -- Understand data compression ratios
Sync Time Estimate -- Predict final synchronization duration
Bandwidth Testing -- Measure network throughput to copy node

Common Use Cases

Check migration status -- Get overall migration phase and progress
Monitor library progress -- Track which libraries are migrating
Identify failures -- Find objects that failed to migrate
Verify completion -- Confirm objects successfully migrated
Plan cutover -- Estimate final sync time and bandwidth
Troubleshoot -- Investigate migration failures and bottlenecks

Quick Examples

Check overall migration status

ibmi tool get_migration_manager_info --tools "$SKILL_DIR/tools/"

List objects being migrated

ibmi tool list_library_migration --tools "$SKILL_DIR/tools/"

Find migration failures

ibmi tool list_migration_failures --tools "$SKILL_DIR/tools/"

Estimate final sync time

ibmi tool estimate_final_sync_time --tools "$SKILL_DIR/tools/"

Pre-built Tools

The tools/migrate-while-active.yaml file provides 9 ready-to-use tools:

Tool	Description
`get_migration_manager_info`	Overall migration state, phase, and nodes
`list_library_migration`	Library objects being tracked for migration
`list_ifs_migration`	IFS objects being tracked for migration
`list_migrated_libraries`	Successfully migrated library objects
`list_migrated_ifs`	Successfully migrated IFS objects
`list_migration_failures`	Library migration objects with failures
`get_data_compression_factor`	Compression ratios by type
`estimate_final_sync_time`	Final synchronization time estimate
`check_migration_network_bandwidth`	Network bandwidth to copy node

ibmi tool <tool_name> --tools "$SKILL_DIR/tools/"          # Execute
ibmi tool <tool_name> --tools "$SKILL_DIR/tools/" --dry-run # Preview SQL
ibmi tools show <tool_name> --tools "$SKILL_DIR/tools/"     # View details

Reference Documentation

Migration Services Catalog -- Available SQL services
Example SQL Patterns -- Working query examples
IBM MIGRATION_MANAGER_INFO -- View documentation

More from this repository

same repository

ibmi

ajshedivy/ibmi-agent-skills

Core skill for working with IBM i systems through the ibmi CLI. Covers text-to-SQL methodology, Db2 for i conventions, schema discovery, multi-system configuration, and — critically — agent scripting patterns (automatic JSON-when-piped, semantic exit codes, NDJSON streaming, dry-run planning, watch mode, multi-system workflows). Use this skill as the foundation for ANY IBM i task: running queries, exploring the database, configuring systems, writing bash/agent scripts that target IBM i, or composing pipelines that need structured output and reliable error handling.

2026-04-243

application

ajshedivy/ibmi-agent-skills

Query and explore IBM i application objects including CL commands, data areas, data queues, programs, environment variables, exit programs, and watches via SQL services. Use when user asks about: (1) CL command attributes or discovery, (2) data area values or inventory, (3) data queue status and messages, (4) program information (ILE/OPM), (5) environment variables, (6) registered exit programs, (7) watch sessions, (8) user spaces or user indexes, or (9) replacing DSPCMD, DSPDTAARA, DSPLIB, DSPPGM commands.

2026-04-243

backup-and-recovery

ajshedivy/ibmi-agent-skills

Query and analyze IBM i backup and recovery resources including save files, save file contents, media libraries, and tape cartridges via SQL services. Use when user asks about: (1) save file history or contents, (2) finding where an object was saved, (3) media library device status, (4) tape cartridge inventory, (5) backup verification, or (6) replacing DSPSAVF, WRKTAP, WRKMLBRM commands.

2026-04-243

communication

ajshedivy/ibmi-agent-skills

Monitor and analyze IBM i network and communication resources including TCP/IP connections, network interfaces, routing, HTTP servers, and DNS configuration via SQL services. Use when user asks about: (1) active network connections and traffic, (2) network interface status and IP addresses, (3) routing tables, (4) HTTP server configuration and status, (5) TCP/IP settings and hostname, (6) NTP/SNTP time synchronization, (7) network attributes, or (8) replacing NETSTAT, WRKTCPSTS, CFGTCP, WRKhttpsrvr commands.

2026-04-243

configuration

ajshedivy/ibmi-agent-skills

Query IBM i system configuration including system values, hardware resources, device status, environment variables, and JVM settings via SQL services. Use when user asks about: (1) system value settings like QSECURITY or QCCSID, (2) security-related system values, (3) hardware resource inventory, (4) controller, device, or line status, (5) environment variable settings, (6) active JVM information, (7) replacing DSPSYSVAL, DSPHDWRSC, WRKCFGSTS, WRKENVVAR commands, or (8) any system configuration review.

2026-04-243

database-application

ajshedivy/ibmi-agent-skills

Analyze IBM i SQL application behavior including error logs, statement parsing, SQLCODE lookups, and system limits. Use when user asks about: (1) SQL errors in applications or error log analysis, (2) most frequent SQL errors, (3) parsing SQL statements to find referenced objects, (4) looking up SQLCODE meanings, (5) properly delimiting SQL identifiers, (6) system size limits for files or indexes, or (7) objects approaching maximum capacity.

2026-04-243