InterForm Manual - System & Method

Recommendations

Info

Appendix S - Install/Upgrade on iASP machines Requirements Moving to iASP 544 User’s Manual for InterForm400 ® It is possible to run InterForm400 on a single iASP (independent auxiliary storage pool). There are a few things you will need to setup differently, when you are running iASP compared to the normal SYSASP as listed below: a) Any programs called by InterForm400 must be placed in libraries within the same iASP or SYSASP. b) The subsystems used by InterForm400 cannot be placed in the iASP (e.g. in library APF3812), but must be in the SYSASP. InterForm400 can help you to copy (and rename if you want) the used subsystems. c) The IPL startup program should start the new subsystems at IPL. d) The user profiles of those that should use the graphical designer will need need to refer to a job description, which refers to the iASP in the INLASPGRP field. e) If you are running V5R3 or V5R4 you will need to create a specific data area: CRTDTAARA DTAARA(QSYS/QWTSBSIASP) TYPE(*CHAR) LEN(20) VALUE('YourAFCSBSYourIASP') TEXT('Allow sbs monitor job to use IASP') AUT(*USE) - to make it possible to run a job with an auxiliary storage pool (ASP) group in its library name space. Refer to how to meet each of these requirements below on page 545 in the section ‘Changing the setup to iASP’. The process of moving to iASP depends on if you are installing InterForm400 for the first time or during an upgrade of InterForm400: First time install First time install on iASP (InterForm400 is not installed in neither SYSASP nor iASP). In order to install InterForm400 on an iASP you can initially run a normal installation. You can e.g. use the RSTLIBPC.JAR program to upload and restore the APF3812NEW library to a specific iASP and run the normal APF3812NEW/APF3812NEW command. During the installation InterForm400 will restore the directories to the iASP and create symbolic links /apf3812Home and /apf3812Mail pointing to //APF3812Home and //APF3812Mail. After that you will need the same setup as described below: Changing the setup to iASP. Moving an existing installation from SYSASP into an iASP If you want to upgrade InterForm400 as well as move from SYSASP to iASP, we recommend first to upgrade to version 2009M08 or higher and make sure it runs stable in the SYSASP before moving it onto the iASP: It is simply good practice not to change too
much at a time, if something should stop working. Doing an upgrade and move to iASP at the same time could make it more difficuilt to find the cause of a problem, if something should occour. If you have an existing installation of InterForm400 in the SYSASP, which you want to move to an iASP, you should first start out by saving the apf3812 library and the directories /apf3812Home and /apf3812mail (including subdirectories). Then rename the apf3812 library (end the subsystems inside and end, save and delete journals and journal receivers inside via the journal menu in InterForm400). Then you can rename the library to e.g. APF3812SAV (not apf3812, apf3812old or apf3812new). Also rename the /apf3812home and /apf3812mail directories. Now restore the apf3812 library and the directories to the iASP: RSTLIB SAVLIB(APF3812) DEV(*SAVF) SAVF(/) RSTASPDEV() RST DEV('/qsys.lib/.lib/.file') OBJ(('/apf3812home' *INCLUDE '//apf3812home')) RST DEV('/qsys.lib/.lib/.file') OBJ(('/apf3812mail' *INCLUDE '//apf3812mail')) If you now upgrade to a 2009M08 version or later, the symbolic links will now be added automatically. If you are not upgrading, you will need to add symbolic links yourself: ADDLNK OBJ('//APF3812Home') NEW LNK('/APF3812Home') ADDLNK OBJ('//APF3812Mail') NEW LNK('/APF3812Mail') where should be exchanged with the name of the iASP, that you are using (do not include the ). Changing the setup to iASP After you have restored (and perhaps upgraded) InterForm400 onto the iASP, you will need to do a few changes to fit the requirements listed in the beginning of this appendix: a) All user exit programs called by InterForm400 must be placed in the same iASP as InterForm400 or in the system ASP. You can generate a list of all user programs called by first changing your job to use an output queue, that is not connected to a physical printer and then creating a spooled file, that lists all cross references in InterForm400: Change the default outq: CHGJOB OUTQ(APF3812/AFC_INPUT1) (or use another outq not connected to a printer) Create the list by running this command: APF3812/PRTXREF (You can also create the report via option '8. Print Resource X-reference' on the InterForm400 service menu). Now you can search the generated spooled file for '*USREXIT' to find all user programs that can be called and from where they are called. b) The subsystems used by InterForm400 cannot be placed in the iASP (e.g. in library APF3812), but must be in the SYSASP, so now you need to refer to new subsystem descriptions. To copy the subsystem descriptions and to refer to the new ones you can select this in InterForm400: 70. Configuration and licences 2. Configure InterForm 400 Now press Enter several times until you get to this screen: InterForm A/S 545
Page 2 and 3:
InterForm A/S Hyldalvej 11 DK-9541
Page 4 and 5:
Table of Contents 4 User’s Manual
Page 6 and 7:
6 User’s Manual for InterForm400
Page 8 and 9:
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
About This Manual This manual is in
Page 18 and 19:
W hat is new in the 2012 versions T
Page 20 and 21:
PCL/PDF output • Images and fonts
Page 22 and 23:
The m odules of InterForm400 Below
Page 24 and 25:
G e ting Started The idea of the fo
Page 26 and 27:
2. Installation Installation/upgrad
Page 28 and 29:
this agreement can be viewed from t
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
4. Work With Overlay/AFC Sample You
Page 40 and 41:
5. About The Print Results Maybe yo
Page 42 and 43:
U nicode, DBCS and multiple codepag
Page 44 and 45:
Page 46 and 47:
® Version: The release number of I
Page 48 and 49:
Copy Overlay from Another Overlay T
Page 50 and 51:
F4=Prompt Gives a list of available
Page 52 and 53:
Forced front page: Controls if the
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Copy Management Copy management is
Page 60 and 61:
Stapling This option defines if the
Page 62 and 63:
The Design Screen Note: Refer to Ap
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
NW: Radius in pels for the North We
Page 70 and 71:
Endpoint 2 From Top: Inches, pels a
Page 72 and 73:
7=INK (fill pattern for succeeding
Page 74 and 75:
8=TABULATOR (Paragraph tabulation)
Page 76 and 77:
� WARNING � If two or more over
Page 78 and 79:
� WARNING � 78 User’s Manual
Page 80 and 81:
I=IM A G E 80 User’s Manual for I
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
How the sequence lines in overlay d
Page 88 and 89:
Step 1. Making a Work Copy of the O
Page 90 and 91:
Step 4. Edit Subject Text Now we wi
Page 92 and 93:
Step 6. Making Equal Distance Betwe
Page 94 and 95:
Step 7. Making Equal Distance betwe
Page 96 and 97:
Step 8. Defining the Column Headers
Page 98 and 99:
Step 9. Defining the Item Line Bars
Page 100 and 101:
The logo now needs to be dimmed in
Page 102 and 103:
You can see that the element is inc
Page 104 and 105:
Step 18. The Result Now we can prev
Page 106 and 107:
Example of Advanced use of Sub-over
Page 108 and 109:
We insert a frame element, select t
Page 110 and 111:
We remap line 1, positions 1-70 and
Page 112 and 113:
Page 2: 112 User’s Manual for Int
Page 114 and 115:
3. Merge Spool Entry with Overlay W
Page 116 and 117:
Page 118 and 119:
You can also see the number of page
Page 120 and 121:
Selector Name: The name you will be
Page 122 and 123:
G e ting Familiar with Overlay Sele
Page 124 and 125:
Step 2. Examining Spool Entry Selec
Page 126 and 127:
Page 128 and 129:
G eneral Description of Auto Forms
Page 130 and 131:
12. Work with Active Subsystem AUTO
Page 132 and 133:
The “INPUT QUEUE” mentioned abo
Page 134 and 135:
Page 136 and 137:
Template AFC-definition to be execu
Page 138 and 139:
AFC Definition Entries The AFC func
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
� NOTE � 148 User’s Manual fo
Page 150 and 151:
� WARNING � ® All exit program
Page 152 and 153:
B=Split spooled file 152 User’s M
Page 154 and 155:
� WARNING � Make sure, that you
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Auto Forms Control Hints Some are s
Page 162 and 163:
G e ting Familiar with Auto Forms C
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
� TIP � 168 User’s Manual for
Page 170 and 171:
further by any sequence line after
Page 172 and 173:
Step 6. Cleaning up processed jobs
Page 174 and 175:
Using a “TEMPLATE” AFC defintio
Page 176 and 177:
Page 178 and 179:
page 141) File-set: The file-set wh
Page 180 and 181:
F13=Select spooled file Press this
Page 182 and 183:
Calling a User Exit Program with th
Page 184 and 185:
� WARNING � All exit programs c
Page 186 and 187:
Example Using Split ® The followin
Page 188 and 189:
Page 190 and 191:
Finishing Definitions This function
Page 192 and 193:
Seal envelope: Seal envelope with w
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Placement of optical marks: Refer t
Page 204 and 205:
How to distribute E-mails and faxes
Page 206 and 207:
2. Key definitions 206 User’s Man
Page 208 and 209:
The variables can be referred to in
Page 210 and 211:
Page 212 and 213:
The addresses are identified by the
Page 214 and 215:
2. User profile 3. Organisation 3=I
Page 216 and 217:
The directory is a subdirectory ins
Page 218 and 219:
Page 220 and 221:
The File Naming Finishing Definitio
Page 222 and 223:
Page 224 and 225:
5. Page selections and Document bre
Page 226 and 227:
Define Level Break Conditions for F
Page 228 and 229:
Page selection criteria 228 User’
Page 230 and 231:
Using the Finishing Definition with
Page 232 and 233:
Page 234 and 235:
� WARNING � The Finishing defin
Page 236 and 237:
Here you can state how many of the
Page 238 and 239:
Page 240 and 241:
Totals 2 = Text constant: 240 User
Page 242 and 243:
Footer If only 1 total page This de
Page 244 and 245:
Page 246 and 247:
Page type definitions The next issu
Page 248 and 249:
Later you can search for various va
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
S ort Definitions This function is
Page 260 and 261:
The functionality of F13 and F18 is
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
G e ting familiar with PDF Bookmark
Page 270 and 271:
Level-3 270 User’s Manual for Int
Page 272 and 273:
G eneral Description of OSC (Output
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Getting Familiar with OSC (Output S
Page 280 and 281:
Define Sort Fields: 280 User’s Ma
Page 282 and 283:
Specify automatic start scheduling:
Page 284 and 285:
Configuration and licenses If you w
Page 286 and 287:
2. Configure InterForm 400 When you
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
3. Configure email With this option
Page 294 and 295:
4. Configure WinPrint WinPrint is a
Page 296 and 297:
® 1. Work with InterForm400 Users
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
4. Work with Fonts 302 User’s Man
Page 304 and 305:
Spacing: Indicates whether the font
Page 306 and 307:
3. Create barcode soft font for PCL
Page 308 and 309:
If you press F6-Create, you get thi
Page 310 and 311:
6. Work with TrueType font for UCS2
Page 312 and 313:
Please note this, when adding print
Page 314 and 315:
Page 316 and 317:
B arcode Support ® InterForm400 cu
Page 318 and 319:
end of transmision enquiry acknow
Page 320 and 321:
Page 322 and 323:
MICR E-13B This font is normally us
Page 324 and 325:
Page 326 and 327:
3. A description is retrieved from
Page 328 and 329:
Step 3. Create font ID for the Aria
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
12. Work with ZEBRA soft fonts When
Page 342 and 343:
This will create an entry in the li
Page 344 and 345:
Page 346 and 347:
Working with black and white images
Page 348 and 349:
Notice that the extension must be e
Page 350 and 351:
12. Work with images in ZEBRA flash
Page 352 and 353:
Page 354 and 355:
7. W ork with palette colors Change
Page 356 and 357:
Here you can specify what drawer nu
Page 358 and 359:
Page 360 and 361:
Page 362 and 363:
9. W ork with AFPDS copy spooled fi
Page 364 and 365:
20. Certificate administration Refe
Page 366 and 367:
1. Work with email groups You can m
Page 368 and 369:
Service Functions The service funct
Page 370 and 371:
7. Print Saved Spooled File from /A
Page 372 and 373:
10. Display resource statistics Sel
Page 374 and 375:
21. Export of InterForm400 resource
Page 376 and 377:
Page 378 and 379:
4. Transfer resources to the produc
Page 380 and 381:
Page 382 and 383:
H ow to create PDF files ® InterFo
Page 384 and 385:
Type choices, press Enter. 384 User
Page 386 and 387:
TITLE, AUTHOR, These fields are ext
Page 388 and 389:
You can not combine duplex overlays
Page 390 and 391:
- indicating that the PDF file is P
Page 392 and 393:
Page 394 and 395:
Page 396 and 397:
Page 398 and 399:
Upgrade remote sites If you do not
Page 400 and 401:
A ppendix B - Attaching Printers to
Page 402 and 403:
Changing Device Description from 52
Page 404 and 405:
In case the printer session of your
Page 406 and 407:
Page 408 and 409:
A ppendix C - Printer Types ® The
Page 410 and 411:
Page 412 and 413:
With the AFPDS spooled file you do
Page 414 and 415:
Columns . . . : 1 80 Browse SEU==>
Page 416 and 417:
Note, that the workaround have the
Page 418 and 419:
A ppendix F - Font-ID Information T
Page 420 and 421:
Page 422 and 423:
Typefaces known by PCL-Printers PCL
Page 424 and 425:
A ppendix H - Commands in Spooled F
Page 426 and 427:
Page 428 and 429:
Page 430 and 431:
Page 432 and 433:
Page 434 and 435:
As mentioned before in this chapter
Page 436 and 437:
® A ppendix I - InterForm400 CL Co
Page 438 and 439:
The Import Chart Command The APF381
Page 440 and 441:
AFC and OSC Commands The End Auto F
Page 442 and 443:
The OUTPUT parameter is used to sel
Page 444 and 445:
Page 446 and 447:
Page 448 and 449:
Split definitions will normally be
Page 450 and 451:
The Merge Spooled File PDF Command
Page 452 and 453:
The Send Mails Command The Send Mai
Page 454 and 455:
Other Utility Commands The Edit Pri
Page 456 and 457:
F24=More keys The media type indica
Page 458 and 459:
The command gives you the possibili
Page 460 and 461:
Page 462 and 463:
Page 464 and 465:
Page 466 and 467:
Above we have defined actions for 3
Page 468 and 469:
The Zip Stream File(s) Command The
Page 470 and 471:
The special functions supported for
Page 472 and 473:
Page 474 and 475:
A ppendix L - PDF and PCL Viewing
Page 476 and 477:
\\system\apf3812Home\view. You can
Page 478 and 479:
Appendix M - InterForm400 charts In
Page 480 and 481:
Press F6 to create a new chart: 480
Page 482 and 483:
Define layout of the X-axis When de
Page 484 and 485:
Work with X-axis points You can ass
Page 486 and 487:
Define observation set When selecti
Page 488 and 489:
Page 490 and 491:
&&CHA01 *INT1 OSLO ... (Define obse
Page 492 and 493:
General layout commands Define gene
Page 494 and 495: Y1-/Y2-axis commands Define Y1-axis
Page 496 and 497: X-axis group commands Add/change X-
Page 498 and 499: Observation set commands Add/change
Page 500 and 501: Data commands Add/change data by ID
Page 502 and 503: Appendix N - Sending E-mails from t
Page 504 and 505: 504 User’s Manual for InterForm40
Page 512 and 513: Settings and tools for the design 5
Page 520 and 521: The Result view 520 User’s Manual
Page 524 and 525: Page Management 524 User’s Manual
Page 528 and 529: � WARNING � 528 User’s Manual
Page 532 and 533: Appendix Q - Building functions int
Page 540 and 541: Appendix R - Install/Upgrade on mir
Page 548 and 549: Index 548 User’s Manual for Inter
show all

InterForm Manual - System & Method

Create successful ePaper yourself

Delete template?

Save as template?