On ROS Console.
Why am I getting these DUPLICATED messages?

ST CPCOMM,,,0/SECURITY
ENTER C.L. FOR : .CPCOMM
0 0
CPCOMM DUPLICATED. NEW ID IS CPCOM5
CPCOM5 START
CPCOM5*CCB105500: Configuration processing is complete.

ST SILAS,,,0/SECURITY
ENTER C.L. FOR : .SILAS
0 0
SILAS DUPLICATED. NEW ID IS SILASD
SILASD START
SILASD*System Interface for Legacy Application Systems

Einar

On Tue, 16 May 2023 03:17:53 -0700 (PDT), Einar Flaathe
<einar.a.flaathe@gmail.com> wrote:

>On ROS Console.
>Why am I getting these DUPLICATED messages?
>
>ST CPCOMM,,,0/SECURITY
> ENTER C.L. FOR : .CPCOMM
>0 0
> CPCOMM DUPLICATED. NEW ID IS CPCOM5
> CPCOM5 START
> CPCOM5*CCB105500: Configuration processing is complete.
>
>ST SILAS,,,0/SECURITY
> ENTER C.L. FOR : .SILAS
>0 0
> SILAS DUPLICATED. NEW ID IS SILASD
> SILASD START
> SILASD*System Interface for Legacy Application Systems
>
>Einar

At a guess, because you have print files from previous CPCOMM and
SILAS runs on print queues.

Try typing in "SQ" (without quotation marks, unsolicited console keyin
that will display wich print files are queued to which print queues).
If you have a bunch (technical term of the art meaning "more than a
few") you could probably key in a bunch of "SX runid" keyins to delete
the print files you almost certainly aren't interested in seeing...

On Tuesday, 16 May 2023 at 22:30:24 UTC+2, David W Schroth wrote:
> On Tue, 16 May 2023 03:17:53 -0700 (PDT), Einar Flaathe
> <einar.a...@gmail.com> wrote:
>
> >On ROS Console.
> >Why am I getting these DUPLICATED messages?
> >
> >ST CPCOMM,,,0/SECURITY
> > ENTER C.L. FOR : .CPCOMM
> >0 0
> > CPCOMM DUPLICATED. NEW ID IS CPCOM5
> > CPCOM5 START
> > CPCOM5*CCB105500: Configuration processing is complete.
> >
> >ST SILAS,,,0/SECURITY
> > ENTER C.L. FOR : .SILAS
> >0 0
> > SILAS DUPLICATED. NEW ID IS SILASD
> > SILASD START
> > SILASD*System Interface for Legacy Application Systems
> >
> >Einar
> At a guess, because you have print files from previous CPCOMM and
> SILAS runs on print queues.
>
> Try typing in "SQ" (without quotation marks, unsolicited console keyin
> that will display wich print files are queued to which print queues).
> If you have a bunch (technical term of the art meaning "more than a
> few") you could probably key in a bunch of "SX runid" keyins to delete
> the print files you almost certainly aren't interested in seeing...

You solved my problem!
Now I'm not getting any more DUPLICATED messages.

SQ
PR: 40 FILES 54 PAGES
SX,U SECURITY
39 FILES DELETED VIA SX KEYIN
SQ
PR: 1 FILE 2 PAGES

But what is a run-id, and where do I find it?
Is it like session number?

Thank you David.
Einar

Einar Flaathe wrote:
> On Tuesday, 16 May 2023 at 22:30:24 UTC+2, David W Schroth wrote:
>> On Tue, 16 May 2023 03:17:53 -0700 (PDT), Einar Flaathe
>> <einar.a...@gmail.com> wrote:
>>
>>> On ROS Console.
>>> Why am I getting these DUPLICATED messages?
>>>
>>> ST CPCOMM,,,0/SECURITY
>>> ENTER C.L. FOR : .CPCOMM
>>> 0 0
>>> CPCOMM DUPLICATED. NEW ID IS CPCOM5
>>> CPCOM5 START
>>> CPCOM5*CCB105500: Configuration processing is complete.
>>>
>>> ST SILAS,,,0/SECURITY
>>> ENTER C.L. FOR : .SILAS
>>> 0 0
>>> SILAS DUPLICATED. NEW ID IS SILASD
>>> SILASD START
>>> SILASD*System Interface for Legacy Application Systems
>>>
>>> Einar
>> At a guess, because you have print files from previous CPCOMM and
>> SILAS runs on print queues.
>>
>> Try typing in "SQ" (without quotation marks, unsolicited console keyin
>> that will display wich print files are queued to which print queues).
>> If you have a bunch (technical term of the art meaning "more than a
>> few") you could probably key in a bunch of "SX runid" keyins to delete
>> the print files you almost certainly aren't interested in seeing...
>
> You solved my problem!
> Now I'm not getting any more DUPLICATED messages.
>
> SQ
> PR: 40 FILES 54 PAGES
> SX,U SECURITY
> 39 FILES DELETED VIA SX KEYIN
> SQ
> PR: 1 FILE 2 PAGES
>
> But what is a run-id, and where do I find it?
> Is it like session number?
>
> Thank you David.
> Einar
>

I pretty much answered your questions in my previous post.
"CPCOMM" or "SILASA" are examples of runids, "sq pr *" (or as David puts
it, SQ PR *) shows you what print files you have.
You can supply multiple runids on an SX keyin - up to 4 - separated by
commas. I had not been aware of the SX,U (U has to be Userid) keyin,
that may have been introduced in an Exec level I was not familiar with.

You can have Original runids and Generated runids. When you see
CPCOMM DUPLICATED. NEW ID IS CPCOM5
CPCOMM is the original and CPCOMS (that has to be an S, not a 5) is the
generated one, they only differ if there is some trace of a previous
CPCOMM still in the system.

On Wednesday, 17 May 2023 at 08:01:35 UTC+2, Don Spam's Reckless Son wrote:
> Einar Flaathe wrote:
> > On Tuesday, 16 May 2023 at 22:30:24 UTC+2, David W Schroth wrote:
> >> On Tue, 16 May 2023 03:17:53 -0700 (PDT), Einar Flaathe
> >> <einar.a...@gmail.com> wrote:
> >>
> >>> On ROS Console.
> >>> Why am I getting these DUPLICATED messages?
> >>>
> >>> ST CPCOMM,,,0/SECURITY
> >>> ENTER C.L. FOR : .CPCOMM
> >>> 0 0
> >>> CPCOMM DUPLICATED. NEW ID IS CPCOM5
> >>> CPCOM5 START
> >>> CPCOM5*CCB105500: Configuration processing is complete.
> >>>
> >>> ST SILAS,,,0/SECURITY
> >>> ENTER C.L. FOR : .SILAS
> >>> 0 0
> >>> SILAS DUPLICATED. NEW ID IS SILASD
> >>> SILASD START
> >>> SILASD*System Interface for Legacy Application Systems
> >>>
> >>> Einar
> >> At a guess, because you have print files from previous CPCOMM and
> >> SILAS runs on print queues.
> >>
> >> Try typing in "SQ" (without quotation marks, unsolicited console keyin
> >> that will display wich print files are queued to which print queues).
> >> If you have a bunch (technical term of the art meaning "more than a
> >> few") you could probably key in a bunch of "SX runid" keyins to delete
> >> the print files you almost certainly aren't interested in seeing...
> >
> > You solved my problem!
> > Now I'm not getting any more DUPLICATED messages.
> >
> > SQ
> > PR: 40 FILES 54 PAGES
> > SX,U SECURITY
> > 39 FILES DELETED VIA SX KEYIN
> > SQ
> > PR: 1 FILE 2 PAGES
> >
> > But what is a run-id, and where do I find it?
> > Is it like session number?
> >
> > Thank you David.
> > Einar
> >
> I pretty much answered your questions in my previous post.
> "CPCOMM" or "SILASA" are examples of runids, "sq pr *" (or as David puts
> it, SQ PR *) shows you what print files you have.
> You can supply multiple runids on an SX keyin - up to 4 - separated by
> commas. I had not been aware of the SX,U (U has to be Userid) keyin,
> that may have been introduced in an Exec level I was not familiar with.
>
> You can have Original runids and Generated runids. When you see
> CPCOMM DUPLICATED. NEW ID IS CPCOM5
> CPCOMM is the original and CPCOMS (that has to be an S, not a 5) is the
> generated one, they only differ if there is some trace of a previous
> CPCOMM still in the system.

Thank you for the explanation of what a runid is!
Einar

On Wednesday, 17 May 2023 at 11:58:22 UTC+2, Einar Flaathe wrote:
> On Wednesday, 17 May 2023 at 08:01:35 UTC+2, Don Spam's Reckless Son wrote:
> > Einar Flaathe wrote:
> > > On Tuesday, 16 May 2023 at 22:30:24 UTC+2, David W Schroth wrote:
> > >> On Tue, 16 May 2023 03:17:53 -0700 (PDT), Einar Flaathe
> > >> <einar.a...@gmail.com> wrote:
> > >>
> > >>> On ROS Console.
> > >>> Why am I getting these DUPLICATED messages?
> > >>>
> > >>> ST CPCOMM,,,0/SECURITY
> > >>> ENTER C.L. FOR : .CPCOMM
> > >>> 0 0
> > >>> CPCOMM DUPLICATED. NEW ID IS CPCOM5
> > >>> CPCOM5 START
> > >>> CPCOM5*CCB105500: Configuration processing is complete.
> > >>>
> > >>> ST SILAS,,,0/SECURITY
> > >>> ENTER C.L. FOR : .SILAS
> > >>> 0 0
> > >>> SILAS DUPLICATED. NEW ID IS SILASD
> > >>> SILASD START
> > >>> SILASD*System Interface for Legacy Application Systems
> > >>>
> > >>> Einar
> > >> At a guess, because you have print files from previous CPCOMM and
> > >> SILAS runs on print queues.
> > >>
> > >> Try typing in "SQ" (without quotation marks, unsolicited console keyin
> > >> that will display wich print files are queued to which print queues)..
> > >> If you have a bunch (technical term of the art meaning "more than a
> > >> few") you could probably key in a bunch of "SX runid" keyins to delete
> > >> the print files you almost certainly aren't interested in seeing...
> > >
> > > You solved my problem!
> > > Now I'm not getting any more DUPLICATED messages.
> > >
> > > SQ
> > > PR: 40 FILES 54 PAGES
> > > SX,U SECURITY
> > > 39 FILES DELETED VIA SX KEYIN
> > > SQ
> > > PR: 1 FILE 2 PAGES
> > >
> > > But what is a run-id, and where do I find it?
> > > Is it like session number?
> > >
> > > Thank you David.
> > > Einar
> > >
> > I pretty much answered your questions in my previous post.
> > "CPCOMM" or "SILASA" are examples of runids, "sq pr *" (or as David puts
> > it, SQ PR *) shows you what print files you have.
> > You can supply multiple runids on an SX keyin - up to 4 - separated by
> > commas. I had not been aware of the SX,U (U has to be Userid) keyin,
> > that may have been introduced in an Exec level I was not familiar with.
> >
> > You can have Original runids and Generated runids. When you see
> > CPCOMM DUPLICATED. NEW ID IS CPCOM5
> > CPCOMM is the original and CPCOMS (that has to be an S, not a 5) is the
> > generated one, they only differ if there is some trace of a previous
> > CPCOMM still in the system.
> Thank you for the explanation of what a runid is!
> Einar

The reason why I had so many print files, was because I was trying to generate
a printout to the default PRINTER declared in sys1.cfg of PS2200.

I was told to do the following:

To create a print file (either SOS or ROS) do the following:

>@CAT,P PRINT
>@PRT <--- Or whatever else is to be printed
>@BRKPT PRINT$

To print this file in SOS: >@SYM,U PRINT,,PR [two commas]

To print this file in ROS: >@P22PRINT PRINT.,PR [period comma]

After, it may be necessary to enter the following on the SOS console to init the print queue: >SM PR I

But the >@BRKPT PRINT$ resulted in the following response:
BRKPT PRINT$ IS ILLEGAL FOR DEMAND

I found this explanation about the message:
The @BRKPT PRINT$ statement was used from a demand terminal before the
@BRKPT PRINT$/file.

I don’t know what to do – there is no mention of a /file in the instruction.

Einar

On 5/17/2023 8:00 AM, Einar Flaathe wrote:
> On Wednesday, 17 May 2023 at 11:58:22 UTC+2, Einar Flaathe wrote:
>> On Wednesday, 17 May 2023 at 08:01:35 UTC+2, Don Spam's Reckless Son wrote:
>>> Einar Flaathe wrote:
>>>> On Tuesday, 16 May 2023 at 22:30:24 UTC+2, David W Schroth wrote:
>>>>> On Tue, 16 May 2023 03:17:53 -0700 (PDT), Einar Flaathe
>>>>> <einar.a...@gmail.com> wrote:
>>>>>
>>>>>> On ROS Console.
>>>>>> Why am I getting these DUPLICATED messages?
>>>>>>
>>>>>> ST CPCOMM,,,0/SECURITY
>>>>>> ENTER C.L. FOR : .CPCOMM
>>>>>> 0 0
>>>>>> CPCOMM DUPLICATED. NEW ID IS CPCOM5
>>>>>> CPCOM5 START
>>>>>> CPCOM5*CCB105500: Configuration processing is complete.
>>>>>>
>>>>>> ST SILAS,,,0/SECURITY
>>>>>> ENTER C.L. FOR : .SILAS
>>>>>> 0 0
>>>>>> SILAS DUPLICATED. NEW ID IS SILASD
>>>>>> SILASD START
>>>>>> SILASD*System Interface for Legacy Application Systems
>>>>>>
>>>>>> Einar
>>>>> At a guess, because you have print files from previous CPCOMM and
>>>>> SILAS runs on print queues.
>>>>>
>>>>> Try typing in "SQ" (without quotation marks, unsolicited console keyin
>>>>> that will display wich print files are queued to which print queues).
>>>>> If you have a bunch (technical term of the art meaning "more than a
>>>>> few") you could probably key in a bunch of "SX runid" keyins to delete
>>>>> the print files you almost certainly aren't interested in seeing...
>>>>
>>>> You solved my problem!
>>>> Now I'm not getting any more DUPLICATED messages.
>>>>
>>>> SQ
>>>> PR: 40 FILES 54 PAGES
>>>> SX,U SECURITY
>>>> 39 FILES DELETED VIA SX KEYIN
>>>> SQ
>>>> PR: 1 FILE 2 PAGES
>>>>
>>>> But what is a run-id, and where do I find it?
>>>> Is it like session number?
>>>>
>>>> Thank you David.
>>>> Einar
>>>>
>>> I pretty much answered your questions in my previous post.
>>> "CPCOMM" or "SILASA" are examples of runids, "sq pr *" (or as David puts
>>> it, SQ PR *) shows you what print files you have.
>>> You can supply multiple runids on an SX keyin - up to 4 - separated by
>>> commas. I had not been aware of the SX,U (U has to be Userid) keyin,
>>> that may have been introduced in an Exec level I was not familiar with.
>>>
>>> You can have Original runids and Generated runids. When you see
>>> CPCOMM DUPLICATED. NEW ID IS CPCOM5
>>> CPCOMM is the original and CPCOMS (that has to be an S, not a 5) is the
>>> generated one, they only differ if there is some trace of a previous
>>> CPCOMM still in the system.
>> Thank you for the explanation of what a runid is!
>> Einar
>
> The reason why I had so many print files, was because I was trying to generate
> a printout to the default PRINTER declared in sys1.cfg of PS2200.
>
> I was told to do the following:
>
> To create a print file (either SOS or ROS) do the following:
>
>> @CAT,P PRINT
>> @PRT <--- Or whatever else is to be printed
>> @BRKPT PRINT$
>
> To print this file in SOS: >@SYM,U PRINT,,PR [two commas]
>
> To print this file in ROS: >@P22PRINT PRINT.,PR [period comma]
>
> After, it may be necessary to enter the following on the SOS console to init the print queue: >SM PR I
>
> But the >@BRKPT PRINT$ resulted in the following response:
> BRKPT PRINT$ IS ILLEGAL FOR DEMAND
>
> I found this explanation about the message:
> The @BRKPT PRINT$ statement was used from a demand terminal before the
> @BRKPT PRINT$/file.
>
> I don’t know what to do – there is no mention of a /file in the instruction.

You need to breakpoint print$ to the file before you print whatever you
want, then breakpoint back to the terminal when you are done, before the
@SYM.

So modifying your example,

>>> @CAT,P PRINT

@brkpt print$/print

>>> @PRT <--- Or whatever else is to be printed
>>> @BRKPT PRINT$
>>

Then you can do the @SYM, or whatever to actually get the file printed.

--
- Stephen Fuld
(e-mail address disguised to prevent spam)

On Wednesday, 17 May 2023 at 18:16:16 UTC+2, Stephen Fuld wrote:
> On 5/17/2023 8:00 AM, Einar Flaathe wrote:
> > On Wednesday, 17 May 2023 at 11:58:22 UTC+2, Einar Flaathe wrote:
> >> On Wednesday, 17 May 2023 at 08:01:35 UTC+2, Don Spam's Reckless Son wrote:
> >>> Einar Flaathe wrote:
> >>>> On Tuesday, 16 May 2023 at 22:30:24 UTC+2, David W Schroth wrote:
> >>>>> On Tue, 16 May 2023 03:17:53 -0700 (PDT), Einar Flaathe
> >>>>> <einar.a...@gmail.com> wrote:
> >>>>>
> >>>>>> On ROS Console.
> >>>>>> Why am I getting these DUPLICATED messages?
> >>>>>>
> >>>>>> ST CPCOMM,,,0/SECURITY
> >>>>>> ENTER C.L. FOR : .CPCOMM
> >>>>>> 0 0
> >>>>>> CPCOMM DUPLICATED. NEW ID IS CPCOM5
> >>>>>> CPCOM5 START
> >>>>>> CPCOM5*CCB105500: Configuration processing is complete.
> >>>>>>
> >>>>>> ST SILAS,,,0/SECURITY
> >>>>>> ENTER C.L. FOR : .SILAS
> >>>>>> 0 0
> >>>>>> SILAS DUPLICATED. NEW ID IS SILASD
> >>>>>> SILASD START
> >>>>>> SILASD*System Interface for Legacy Application Systems
> >>>>>>
> >>>>>> Einar
> >>>>> At a guess, because you have print files from previous CPCOMM and
> >>>>> SILAS runs on print queues.
> >>>>>
> >>>>> Try typing in "SQ" (without quotation marks, unsolicited console keyin
> >>>>> that will display wich print files are queued to which print queues).
> >>>>> If you have a bunch (technical term of the art meaning "more than a
> >>>>> few") you could probably key in a bunch of "SX runid" keyins to delete
> >>>>> the print files you almost certainly aren't interested in seeing...
> >>>>
> >>>> You solved my problem!
> >>>> Now I'm not getting any more DUPLICATED messages.
> >>>>
> >>>> SQ
> >>>> PR: 40 FILES 54 PAGES
> >>>> SX,U SECURITY
> >>>> 39 FILES DELETED VIA SX KEYIN
> >>>> SQ
> >>>> PR: 1 FILE 2 PAGES
> >>>>
> >>>> But what is a run-id, and where do I find it?
> >>>> Is it like session number?
> >>>>
> >>>> Thank you David.
> >>>> Einar
> >>>>
> >>> I pretty much answered your questions in my previous post.
> >>> "CPCOMM" or "SILASA" are examples of runids, "sq pr *" (or as David puts
> >>> it, SQ PR *) shows you what print files you have.
> >>> You can supply multiple runids on an SX keyin - up to 4 - separated by
> >>> commas. I had not been aware of the SX,U (U has to be Userid) keyin,
> >>> that may have been introduced in an Exec level I was not familiar with.
> >>>
> >>> You can have Original runids and Generated runids. When you see
> >>> CPCOMM DUPLICATED. NEW ID IS CPCOM5
> >>> CPCOMM is the original and CPCOMS (that has to be an S, not a 5) is the
> >>> generated one, they only differ if there is some trace of a previous
> >>> CPCOMM still in the system.
> >> Thank you for the explanation of what a runid is!
> >> Einar
> >
> > The reason why I had so many print files, was because I was trying to generate
> > a printout to the default PRINTER declared in sys1.cfg of PS2200.
> >
> > I was told to do the following:
> >
> > To create a print file (either SOS or ROS) do the following:
> >
> >> @CAT,P PRINT
> >> @PRT <--- Or whatever else is to be printed
> >> @BRKPT PRINT$
> >
> > To print this file in SOS: >@SYM,U PRINT,,PR [two commas]
> >
> > To print this file in ROS: >@P22PRINT PRINT.,PR [period comma]
> >
> > After, it may be necessary to enter the following on the SOS console to init the print queue: >SM PR I
> >
> > But the >@BRKPT PRINT$ resulted in the following response:
> > BRKPT PRINT$ IS ILLEGAL FOR DEMAND
> >
> > I found this explanation about the message:
> > The @BRKPT PRINT$ statement was used from a demand terminal before the
> > @BRKPT PRINT$/file.
> >
> > I don’t know what to do – there is no mention of a /file in the instruction.
> You need to breakpoint print$ to the file before you print whatever you
> want, then breakpoint back to the terminal when you are done, before the
> @SYM.
>
> So modifying your example,
>
> >>> @CAT,P PRINT
>
> @brkpt print$/print
> >>> @PRT <--- Or whatever else is to be printed
> >>> @BRKPT PRINT$
> >>
> Then you can do the @SYM, or whatever to actually get the file printed.
>
>
> --
> - Stephen Fuld
> (e-mail address disguised to prevent spam)

Thank you for your help Stephen!

But I'm still getting : BRKPT PRINT$ IS ILLEGAL FOR DEMAND
and even: INPUT FILE IS EMPTY
I thought that @PRT in this context would output the MFD to the print file too - not only to my screen.

>@CAT,P PRINT
>E:244433 file is already catalogued.

>@brkpt print$/print
>FAC STATUS 400010000000 ON ATTEMPTED ASG/USE

>@prt

>@BRKPT PRINT$
>BRKPT PRINT$ IS ILLEGAL FOR DEMAND

>@P22PRINT PRINT.,PR
>P22PRINT 3R1B (180824 1640:30) 2023 May 18 Thu 1138:25
>INPUT FILE IS EMPTY

SOS Console:
SQ
NO PRINT/PUNCH FILES QUEUED

Einar

On Thursday, 18 May 2023 at 12:08:03 UTC+2, Einar Flaathe wrote:
> On Wednesday, 17 May 2023 at 18:16:16 UTC+2, Stephen Fuld wrote:
> > On 5/17/2023 8:00 AM, Einar Flaathe wrote:
> > > On Wednesday, 17 May 2023 at 11:58:22 UTC+2, Einar Flaathe wrote:
> > >> On Wednesday, 17 May 2023 at 08:01:35 UTC+2, Don Spam's Reckless Son wrote:
> > >>> Einar Flaathe wrote:
> > >>>> On Tuesday, 16 May 2023 at 22:30:24 UTC+2, David W Schroth wrote:
> > >>>>> On Tue, 16 May 2023 03:17:53 -0700 (PDT), Einar Flaathe
> > >>>>> <einar.a...@gmail.com> wrote:
> > >>>>>
> > >>>>>> On ROS Console.
> > >>>>>> Why am I getting these DUPLICATED messages?
> > >>>>>>
> > >>>>>> ST CPCOMM,,,0/SECURITY
> > >>>>>> ENTER C.L. FOR : .CPCOMM
> > >>>>>> 0 0
> > >>>>>> CPCOMM DUPLICATED. NEW ID IS CPCOM5
> > >>>>>> CPCOM5 START
> > >>>>>> CPCOM5*CCB105500: Configuration processing is complete.
> > >>>>>>
> > >>>>>> ST SILAS,,,0/SECURITY
> > >>>>>> ENTER C.L. FOR : .SILAS
> > >>>>>> 0 0
> > >>>>>> SILAS DUPLICATED. NEW ID IS SILASD
> > >>>>>> SILASD START
> > >>>>>> SILASD*System Interface for Legacy Application Systems
> > >>>>>>
> > >>>>>> Einar
> > >>>>> At a guess, because you have print files from previous CPCOMM and
> > >>>>> SILAS runs on print queues.
> > >>>>>
> > >>>>> Try typing in "SQ" (without quotation marks, unsolicited console keyin
> > >>>>> that will display wich print files are queued to which print queues).
> > >>>>> If you have a bunch (technical term of the art meaning "more than a
> > >>>>> few") you could probably key in a bunch of "SX runid" keyins to delete
> > >>>>> the print files you almost certainly aren't interested in seeing....
> > >>>>
> > >>>> You solved my problem!
> > >>>> Now I'm not getting any more DUPLICATED messages.
> > >>>>
> > >>>> SQ
> > >>>> PR: 40 FILES 54 PAGES
> > >>>> SX,U SECURITY
> > >>>> 39 FILES DELETED VIA SX KEYIN
> > >>>> SQ
> > >>>> PR: 1 FILE 2 PAGES
> > >>>>
> > >>>> But what is a run-id, and where do I find it?
> > >>>> Is it like session number?
> > >>>>
> > >>>> Thank you David.
> > >>>> Einar
> > >>>>
> > >>> I pretty much answered your questions in my previous post.
> > >>> "CPCOMM" or "SILASA" are examples of runids, "sq pr *" (or as David puts
> > >>> it, SQ PR *) shows you what print files you have.
> > >>> You can supply multiple runids on an SX keyin - up to 4 - separated by
> > >>> commas. I had not been aware of the SX,U (U has to be Userid) keyin,
> > >>> that may have been introduced in an Exec level I was not familiar with.
> > >>>
> > >>> You can have Original runids and Generated runids. When you see
> > >>> CPCOMM DUPLICATED. NEW ID IS CPCOM5
> > >>> CPCOMM is the original and CPCOMS (that has to be an S, not a 5) is the
> > >>> generated one, they only differ if there is some trace of a previous
> > >>> CPCOMM still in the system.
> > >> Thank you for the explanation of what a runid is!
> > >> Einar
> > >
> > > The reason why I had so many print files, was because I was trying to generate
> > > a printout to the default PRINTER declared in sys1.cfg of PS2200.
> > >
> > > I was told to do the following:
> > >
> > > To create a print file (either SOS or ROS) do the following:
> > >
> > >> @CAT,P PRINT
> > >> @PRT <--- Or whatever else is to be printed
> > >> @BRKPT PRINT$
> > >
> > > To print this file in SOS: >@SYM,U PRINT,,PR [two commas]
> > >
> > > To print this file in ROS: >@P22PRINT PRINT.,PR [period comma]
> > >
> > > After, it may be necessary to enter the following on the SOS console to init the print queue: >SM PR I
> > >
> > > But the >@BRKPT PRINT$ resulted in the following response:
> > > BRKPT PRINT$ IS ILLEGAL FOR DEMAND
> > >
> > > I found this explanation about the message:
> > > The @BRKPT PRINT$ statement was used from a demand terminal before the
> > > @BRKPT PRINT$/file.
> > >
> > > I don’t know what to do – there is no mention of a /file in the instruction.
> > You need to breakpoint print$ to the file before you print whatever you
> > want, then breakpoint back to the terminal when you are done, before the
> > @SYM.
> >
> > So modifying your example,
> >
> > >>> @CAT,P PRINT
> >
> > @brkpt print$/print
> > >>> @PRT <--- Or whatever else is to be printed
> > >>> @BRKPT PRINT$
> > >>
> > Then you can do the @SYM, or whatever to actually get the file printed.
> >
> >
> > --
> > - Stephen Fuld
> > (e-mail address disguised to prevent spam)
> Thank you for your help Stephen!
>
> But I'm still getting : BRKPT PRINT$ IS ILLEGAL FOR DEMAND
> and even: INPUT FILE IS EMPTY
> I thought that @PRT in this context would output the MFD to the print file too - not only to my screen.
>
> >@CAT,P PRINT
> >E:244433 file is already catalogued.
>
> >@brkpt print$/print
> >FAC STATUS 400010000000 ON ATTEMPTED ASG/USE
>
> >@prt
>
> >@BRKPT PRINT$
> >BRKPT PRINT$ IS ILLEGAL FOR DEMAND
> >@P22PRINT PRINT.,PR
> >P22PRINT 3R1B (180824 1640:30) 2023 May 18 Thu 1138:25
> >INPUT FILE IS EMPTY
>
> SOS Console:
> SQ
> NO PRINT/PUNCH FILES QUEUED
>
> Einar

I tried it again - and this time IT WORKED!!!

Enter your user-id/password and clearance level:

*UNISYS 1100 Operating System Level 49R4.30PSE (RSI)*
Current session number: 254
Previous session was: THU 18 MAY 2023 12:52:04 CEST
@run ps2200,0,ps2200
DATE: 2023-05-18 TIME: 12:55:32 CEST
@CAT,P PRINT
E:244433 file is already catalogued.
@brkpt print$/print
@prt
@BRKPT PRINT$
@P22PRINT PRINT.,PR
P22PRINT 3R1B (180824 1640:30) 2023 May 18 Thu 1257:27
PRINTED PS2200*PRINT(1), TRACKS=7 EPAGES=10 ON SOS QUEUE PR.