Topic - How application profiles are stored

Application profiles are stored in the session profile.

• For example, suppose that you have started a 3270 Display session from a session profile named My3270Host.
• Suppose also that while you are running the session, you create a ZipPrint application profile named MyDocType1.
• When you click OK to close the Custom Application Window, Host On-Demand saves the new application profile MyDocType1 inside the My3270Host session profile.
• If you create other ZipPrint application profiles while running a session started from the My3270Host session profile, those new profiles also are saved inside the My3270Host session profile.

When you copy a session profile, any ZipPrint application profiles inside the session profile are also copied.

• In the preceding example, if you make a copy of the My3270Host session profile and rename the copy to My3270Host2, then My3270Host2 contains all the ZipPrint application profiles from My3270Host.
• If you start a session from the My3270Host2 session profile, then you can access all the ZipPrint application profiles that were copied from My3270Host.

Therefore, a system administrator can create a session profile, create ZipPrint application profiles inside the session profile, and distribute the session profile to end users. End users can then use the ZipPrint application profiles stored in the session profile.

When you delete an application profile, Host On-Demand erases the application profile from the session profile.