Ricoh InfoPrint Pro C900AFP InfoPrint Manager - Page 175

Changing the sample DCF advanced information, Debugging your changed DCF, Server Log

Page 175 highlights

PRTQUEUE :: target-destination-name DEST :: Debugging your changed DCF: The sample DCF contains a DEBUG statement that is commented out. To use this statement to check your DCF: 1. Uncomment the DEBUG statement in the DCF that you changed. 2. Save the file. 3. Stop the MVS Download receiver that uses this DCF. 4. Restart the MVS Download receiver that uses this DCF. 5. Submit a job from MVS that runs through this MVS Download receiver. Information will be written into the server log. You can view the server log by clicking the Server Log item in the left pane of the Management Console. 6. Once you are satisfied with the results, open the DCF and comment the DEBUG statement out again. 7. Save the file. 8. Stop the MVS Download receiver that uses this DCF. 9. Restart the MVS Download receiver that uses this DCF. Changing the sample DCF advanced information If you use MVS Exit 15, understand that the predefined mvs_keywords are internally converted using Table 13 on page 158.To add lines to the DCF you will need to be aware of these internal mappings and what additional information your lines need to contain. For example, the sample DCF contains the line: DATACK=BLKPOS :: data-fidelity-problem-reported=character But, because in Table 13 on page 158 DATACK maps to -odatac, this line would produce the same results: -odatac=blkpos :: data-fidelity-problem-reported=character When the MVS host actually sends -odatac=blkpos, this mapping statement is used. For information about the actual keywords that the MVS host sends, see Print Services Facility for z/OS: MVS Download, S544-5624, which you can download from the Ricoh Production Print Solutions Company Web site at http://www.infoprint.com. Note: The mvs_definition (all of the information to the left of the control) is case-sensitive and must exactly match the information that comes from the host system for the mapping to be made. Some parameter information is received from the MVS host as -o keywords and other information is received as sub-keywords of the -opa keyword. For example, CLASS information is received as -opa=class=xxx. When the DCF is processed by an MVS Download receiver, the receiver looks at each mvs_keyword to determine if it will be received from MVS as a keyword or as a sub-keyword of the -opa keyword. The receiver tries to convert the specified mvs_keyword according to Table 13 on page 158. If the receiver does not find a mapping conversion for the specified mvs_keyword, the mvs_keyword is left unchanged. If the result of the conversion begins with -o, the receiver assumes that the mvs_keyword will be received as a keyword. If the result of the conversion Chapter 21. Setting up to use MVS Download 157

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426

PRTQUEUE :: target-destination-name
DEST
::
Debugging your changed DCF:
The sample DCF contains a DEBUG statement that is commented out. To use this
statement to check your DCF:
1.
Uncomment the DEBUG statement in the DCF that you changed.
2.
Save the file.
3.
Stop the MVS Download receiver that uses this DCF.
4.
Restart the MVS Download receiver that uses this DCF.
5.
Submit a job from MVS that runs through this MVS Download receiver.
Information will be written into the server log. You can view the server log by
clicking the
Server Log
item in the left pane of the Management Console.
6.
Once you are satisfied with the results, open the DCF and comment the
DEBUG statement out again.
7.
Save the file.
8.
Stop the MVS Download receiver that uses this DCF.
9.
Restart the MVS Download receiver that uses this DCF.
Changing the sample DCF advanced information
If you use MVS Exit 15, understand that the predefined
mvs_keywords
are internally
converted using Table13 on page 158.To add lines to the DCF you will need to be
aware of these internal mappings and what additional information your lines need
to contain.
For example, the sample DCF contains the line:
DATACK=BLKPOS
:: data-fidelity-problem-reported=character
But, because in Table 13 on page 158
DATACK
maps to
-odatac
, this line would
produce the same results:
-odatac=blkpos
:: data-fidelity-problem-reported=character
When the MVS host actually sends
-odatac=blkpos
, this mapping statement is
used. For information about the actual keywords that the MVS host sends, see
Print Services Facility for z/OS: MVS Download
, S544-5624, which you can download
from the Ricoh Production Print Solutions Company Web site at
Note:
The mvs_definition (all of the information to the left of the control) is
case-sensitive and must exactly match the information that comes from the host
system for the mapping to be made.
Some parameter information is received from the MVS host as
-o
keywords and
other information is received as sub-keywords of the
-opa
keyword. For example,
CLASS information is received as
-opa=class=
xxx
.
When the DCF is processed by an MVS Download receiver, the receiver looks at
each mvs_keyword to determine if it will be received from MVS as a keyword or
as a sub-keyword of the
-opa
keyword. The receiver tries to convert the specified
mvs_keyword according to Table 13 on page 158. If the receiver does not find a
mapping conversion for the specified mvs_keyword, the mvs_keyword is left
unchanged. If the result of the conversion begins with
-o
, the receiver assumes that
the mvs_keyword will be received as a keyword. If the result of the conversion
Chapter 21. Setting up to use MVS Download
157