31.01.2013 Views

InterForm Manual - System & Method

InterForm Manual - System & Method

InterForm Manual - System & Method

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

much at a time, if something should stop working. Doing an upgrade and move to iASP at<br />

the same time could make it more difficuilt to find the cause of a problem, if something<br />

should occour.<br />

If you have an existing installation of <strong>InterForm</strong>400 in the SYSASP, which you want to<br />

move to an iASP, you should first start out by saving the apf3812 library and the directories<br />

/apf3812Home and /apf3812mail (including subdirectories). Then rename the apf3812<br />

library (end the subsystems inside and end, save and delete journals and journal receivers<br />

inside via the journal menu in <strong>InterForm</strong>400). Then you can rename the library to e.g.<br />

APF3812SAV (not apf3812, apf3812old or apf3812new). Also rename the /apf3812home<br />

and /apf3812mail directories. Now restore the apf3812 library and the directories to the<br />

iASP:<br />

RSTLIB SAVLIB(APF3812) DEV(*SAVF) SAVF(/)<br />

RSTASPDEV()<br />

RST DEV('/qsys.lib/.lib/.file')<br />

OBJ(('/apf3812home' *INCLUDE '//apf3812home'))<br />

RST DEV('/qsys.lib/.lib/.file')<br />

OBJ(('/apf3812mail' *INCLUDE '//apf3812mail'))<br />

If you now upgrade to a 2009M08 version or later, the symbolic links will now be added<br />

automatically. If you are not upgrading, you will need to add symbolic links yourself:<br />

ADDLNK OBJ('//APF3812Home') NEW LNK('/APF3812Home')<br />

ADDLNK OBJ('//APF3812Mail') NEW LNK('/APF3812Mail')<br />

where should be exchanged with the name of the iASP, that you are using (do not<br />

include the ).<br />

Changing the setup to iASP<br />

After you have restored (and perhaps upgraded) <strong>InterForm</strong>400 onto the iASP, you will need<br />

to do a few changes to fit the requirements listed in the beginning of this appendix:<br />

a) All user exit programs called by <strong>InterForm</strong>400 must be placed in the same iASP as<br />

<strong>InterForm</strong>400 or in the system ASP.<br />

You can generate a list of all user programs called by first changing your job to use an<br />

output queue, that is not connected to a physical printer and then creating a spooled file,<br />

that lists all cross references in <strong>InterForm</strong>400:<br />

Change the default outq: CHGJOB OUTQ(APF3812/AFC_INPUT1) (or use another outq<br />

not connected to a printer)<br />

Create the list by running this command: APF3812/PRTXREF (You can also create the<br />

report via option '8. Print Resource X-reference' on the <strong>InterForm</strong>400 service menu).<br />

Now you can search the generated spooled file for '*USREXIT' to find all user programs<br />

that can be called and from where they are called.<br />

b) The subsystems used by <strong>InterForm</strong>400 cannot be placed in the iASP (e.g. in<br />

library APF3812), but must be in the SYSASP, so now you need to refer to new<br />

subsystem descriptions. To copy the subsystem descriptions and to refer to the new ones<br />

you can select this in <strong>InterForm</strong>400:<br />

70. Configuration and licences<br />

2. Configure <strong>InterForm</strong> 400<br />

Now press Enter several times until you get to this screen:<br />

<strong>InterForm</strong> A/S 545

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!