| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
G'day All,
A customer upgraded to VMS Version 5.5-1 and is having problems with
the SEND_JBC function. ALL-IN-1 Version 2.4 patched to K602.
The following line in his script does not work any longer
get OA$FUNCTION = "SEND_JBC ENTER_FILE/QUEUE=#PRINT_QUEUE/form=#form -
/DELETE_FILE/FILE_COPIES=#COPIES /FILE_SPECIFICATION=#PRINT_OUTFILE" #PJ
The 2nd parameter #form at times is not getting translated/goes missing.
When printing the form defaults to OA$HLS_80 the default form for ALL-IN-1.
The symbol #PJ is built with other parameters please see below
get #form = "tf_ascii"
.if $JOBMSG eqs OA$Y then get #PJ = "/NOTIFY" -
else get #PJ = "/NO_NOTIFY"
.if $PRT_AFTER nes "" then get #PJ = #PJ "/AFTER_TIME=$PRT_AFTER"
.if $PRT_PRIO nes "" then get #PJ = #PJ "/PRIORITY=$PRT_PRIO"
.if #PRINT_FORM nes "" then get #PJ = #PJ "/FORM_NAME=#PRINT_FORM"
.if #PRINT_JOBNAME nes "" then get #PJ = #PJ "/JOB_NAME=#PRINT_JOBNAME"
If #PRINT_FORM is removed everything works. A copy of the script can
be found on RIPPER::USER$TSC:[SETHI]SECV.SCP, should you require it. I
have read a Topic in here talking about parameter passing but I was not
sure if it is applicable in this case. The Topic is 1338 titled
"Limit of 6 SEND_JBC params for ?".
Thanks for your help in advance
Sunil
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1387.1 | Two /FORM qualifiers | IOSG::NEWLAND | Richard Newland, IOSG, REO1-D/4A | Thu Sep 10 1992 13:08 | 20 |
I've looked at the SECV.SCP script. When #PRINT_FORM is defined it will generate a SEND_JBC command with two /FORM_NAME qualifiers. That is, the /form=#FORM (which will be interpreted as /FORM_NAME) and the /FORM_NAME=#PRINT_FORM from the #PJ symbol. I executed SEND_JBC functions with two /FORM_NAME qualifiers on a system running VMS V5.2 and V5.5. On V5.2 the first /FORM_NAME qualifier is used and on V5.5 the second /FORM_NAME qualifier is used. The SEND_JBC function will build an item list for the $SNDJBC system service with two SJC$_FORM_NAME items. It appears that the new Queue Manager in VMS V5.5 processes the item list differently. If the customer considers this to be a problem you should report it against VMS. The SECV script could be modified so that it does not create calls to SEND_JBC with two /FORM_NAME qualifiers. Richard | |||||
| 1387.2 | Works under 3.0 | GIDDAY::SETHI | Man from Downunder | Mon Dec 21 1992 23:10 | 21 |
Hi,
From VMS engineering I received the following solution for this problem
The order of item list processing is not guaranteed. Thus if
the same item code is put in the item list twice with
different values, the results are uncertain. Most
applications remove duplicates by selecting one of the many
values chosen by the user. Ex: The DCL PRINT command will
always use the last value of the /FORM qualifier provided.
If this is important it should be corrected in ALL-IN-1.
We did some testing here on Version 3.0 and VMS 5.5-1 and it appears as
if the problem has been resolved, we were unable to reproduce the
problem. I couldn't do any testing when the call was opened we did not
have 3.0 available.
Thanks for your help,
Sunil
| |||||