4.15 Q: How Do I Migrate Definitions per Job Net or Group, or between Different Platforms?

Applicable versions and levels

Windows versions: V5.0L20 or later
Solaris versions: 5.0 or later
Linux versions: 5.2, V10.0L10 or later
Linux for Itanium versions: V12.0L10 or later
HP-UX versions:10.0 or later
AIX versions: 10.0 or later

Migrating a project

You cannot output files in control statement format. Use a Systemwalker Operation Manager client or the jobschsetproject command to create a project in advance.

Migrating a group or job nets in a group

[Tasks at the migration source]

If the migration destination is V10.0L20 or 10.1 or later
jobschprint -R <project name>/<group name> >> <group name>.txt
```
Remark: You can specify any file name as the redirection destination.
```
You can specify multiple job net control statements in a single file.
If the migration destination is V10.0L10 or 10.0 or earlier
jobschprint -R <project name>/<group name> > <group name>.txt
```
Remark: You can specify any file name as the redirection destination.
```

[Tasks at the migration destination]

jobschsetgrp -ent <project name> <group name>.txt (*1)

*1: File output from the migration source

Migrating a job nets or job

[Tasks at the migration source]

If the migration destination is V10.0L20 or 10.1 or later

jobschprint -r <project name>/<job net name> >> <job net name>.txt

Remark: You can specify any file name as the redirection destination. 
     You can specify multiple job net control statements in a single file.

If the migration destination is V10.0L10 or 10.0 or earlier
jobschprint -r <project name>/<job net name> > <job net name>.txt
```
Remark: You can specify any file name as the redirection destination.
```

[Tasks at the migration destination]

jobschsetnet -nent <project name> <job net name>.txt (*1)

*1: File output from the migration source