NPR502 1

[kstaff22]

anyone out there ever have to clear out a print que?
>pdt> sl1qShow

SL1 queues of size > 0
Cadence (queue 2 at 0x8c911e8) size : 4
128LowP (queue 3 at 0x8c911fc) size : 3
2Sec (queue 4 at 0x8c91210) size : 3
Print (queue 11 at 0x8c9129c) size : 2501
Idle (queue 12 at 0x8c912b0) size : 7376

total size of above queues: 9887
It's a release 3.00 at a hospital and I'd rather not INI if I can avoid it. The system will not IDU sets---NPR502 (no call registers available for IDU).

 

[Firebird Scrambler]

I'm assuming that you have the larger "Option" system. What are your parameters set in LD 17?.

In the UK, a typical Option 61c at release 3.0 would have settings such as..

REQ ISS
VERSION 2921
RELEASE 3
ISSUE 00 + DepList x210300_cpt

PARM
LPIB 3500
HPIB 3500
500B 800
SL1B 255
RPEB 16
DTIB 70
DTOB 70
NCR 4000
MGCR NULL
CFWS NO
PCML A
ALRM YES
ERRM ERR XBUG AUD
DTRB 100
ABCD NO
TMRK 128
FCDR NEW
PCDR NO
TPO NO
TSO NO
CLID YES
DUR5 NO
MLDN YES
MARP YES
FRPT NEFR
DCUS NULL
DTDT NO
MSCL 350
PMSI
MANU PMS1
PMCR 60

2.3.2 Call Registers (NCR)

Release 23 S/W CP1 2000
Release 23 S/W CP2 3000
Release 23 S/W CP3 / CP4 4000
Release 24 S/W * CP2 3000
Release 24 S/W * CP3 / CP4 4000
Release 25 S/W ** CP3 / CP4 4000
Succession rlse 3 *** CP3 / CP4 4000
Succession rlse 3 *** CP PII 20000
Release 4/ 4.5**** CP3/ CP4 4000
Release 4/ 4.5 CP PII / CP PIV 20000

X21 3/4/4.5 ***/**** HPIB LPIB 500B SL1B
CP1 N/A N/A N/A N/A
CP2 N/A N/A N/A N/A
CP3/4 3500 3500 800 note 1 255
CP PII/IV 3500 3500 2000 note 1 N/A




Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website =

http://somertel.com

linkedin

 

[KCFLHRC]

Cant remember for sure but does changing the call registers require an INI

 

[kstaff22]

The NCR is set at 10k------it's a cpt 3.00.

 

[StanleySteamer]

Seems like there are still lots of call registers available but maybe this will help (from Avaya Solutions)

CRMN0001, Call registers held in Print queue and not released.
Cause
Call Registers were stuck (or not freed after use) at some point due to an unknown reason.

Solution
LD 48 flsh command removes all hanging CR's in the PRINT queue only
Change BDI to NO in CDR block

 

[kstaff22]

StanleySteamer!!!------------yes that was it. as soon as I did the flsh I got some old messages back in december. I can now IDU and also do a stat xsm which also wasn't working.
I wasn't getting an IOD300---instead I was getting a period like it was working but without any message.

pdt> sl1qShow

SL1 queues of size > 0
Cadence (queue 2 at 0x8c911e8) size : 1
128LowP (queue 3 at 0x8c911fc) size : 1
2Sec (queue 4 at 0x8c91210) size : 1
Idle (queue 12 at 0x8c912b0) size : 9816
RAN (queue 14 at 0x8c912d8) size : 1

total size of above queues: 9820

 

[StanleySteamer]

Glad to hear it helped.
Does the BDI thing apply?

 

[kstaff22]

No---they are still using TTY ports for CDR---again---Thanks.
I have used the FLSH command before but most times it was to clear out a bunch of D-Ch messages, but didn't realize it also applied to the print que.