It looks like I am having some type of issue when I
run a job on a remote agent. After the remote agent
executes the job, the Main scheduler displays a
message in the status bar “connection to
Background #2 closed”. This message is displayed
for about 3 – 4 min., at which time 7x24 is taking
100% of the CPU. Both PC’s are running Win2000 and
version 3.4.20 of 7x24.

Any help would be appreciated!

Norm

1. In case if this doesn't happen after local jobs (please make sure to check local jobs first)

In the agent profile properties set the connection type to synchronous (don't use asynchronous mode which is exposed for backward compatibility only).

2. In case if this happens after all jobs (both local and remote)
Please let me know what options you have enabled in the Tools/Options menu, Log page.

: It looks like I am having some type of issue when I
: run a job on a remote agent. After the remote agent
: executes the job, the Main scheduler displays a
: message in the status bar “connection to
: Background #2 closed”. This message is displayed
: for about 3 – 4 min., at which time 7x24 is taking
: 100% of the CPU. Both PC’s are running Win2000 and
: version 3.4.20 of 7x24.

: Any help would be appreciated!

: Norm

It looks like this is only happening on remote jobs.
I check the Remote Host Profile Setup for the remote
PC and Asynchronous Operations was Not checked. The
Tools/Options log tab is set as follows:
Load log on start up: Checked
Maximum number of log records: 500
No other options checked.

Please do the following
In Tools/Options log tab check "Trace enabled" option
Re-run manually one of your remote jobs. when the job runs 24x7 will open a trace window. Do not close it.
Keep watching what is output to that window especially after the job is complete.
Please let us know what you get there. You can use your mouse to copy and paste text from the trace window (same way you copy and paste from any other console window).

PS. Different portions of this trace can be find in *.log files in 24x7 home directory.

: It looks like this is only happening on remote jobs.
: I check the Remote Host Profile Setup for the remote
: PC and Asynchronous Operations was Not checked. The
: Tools/Options log tab is set as follows: Load log on start up: Checked
: Maximum number of log records: 500
: No other options checked.

I checked "Trace enabled" option but do not see a
trace window open. I also checked the *.log file any
additional information but did not see any. What am
I doing wrong. If you have email I can forward setup
screen shots or log files if they would be helpful.

Did you restart the scheduler? Did you check trace option in the agent profile settings?

: I checked "Trace enabled" option but do not see a
: trace window open. I also checked the *.log file any
: additional information but did not see any. What am
: I doing wrong. If you have email I can forward setup
: screen shots or log files if they would be helpful.

Had Trace option set on Master and not Remote. The
following is the trace from the remote PC:
SMI AddRef SMI_TRACE(00FDE608) refCount(7)
DPB AddRef DPB_MARSHALING(06801488) refCount(1)
DPB AddRef DPB_MARSHALING(06801488) refCount(2)
DPB Release DPB_MARSHALING(06801488) refCount(1)
SMI01 Connection(06800020): Create Message: (068006A0), initial size 0 bytes
Write Invoke Request: 30381.uf_remoteexitcode(QLSISBS)

Write LONG: value(16)

Write STRING: value(New Order Create BG Job)

Write INT: value(1)

Write STRING: value(Y)

Write BOOL: value(TRUE)

Write STRING: value()
DPB48 SessionId (00FDDAF8): Invoke : instanceId(000076AD), uf_remoteexitc
ode(QLSISBS), numArgs(6) ASYNCHRONOUS
SMI03 Connection(06800020): Send Message: (068006A0) sequenceNumber(144) Asynchr
onous. ... (00000000)
WSD08 Send: result = 0
WSD07 ReadHeader: Proto = 24576, Len = 87
SMI01 Connection(06800020): Create Message: (07560470), initial size 87 bytes
SMI03 Connection(06800020): Send Message: (068006A0) sequenceNumber(144) Asynchr
onous. SUCCEEDED (00000000)
DPB AddRef DPB_SESSION_SERVICE(068001A0) refCount(3)
DPB Release DPB_MARSHALING(06801488) refCount(0)
DPB40 SessionId (075615C0): Handle Request: DELETE_INSTANCE(4), streamVer(0). SU
CCEEDED (00000000)
SMI Release SMI_TRACE(00FDE608) refCount(6)
DPB AddRef DPB_SESSION_SERVICE(068001A0) refCount(4)

SUCCEEDED (00000000)
DPB Release DPB_SESSION_SERVICE(068001A0) refCount(3)
SMI AddRef SMI_TRACE(00FDE608) refCount(7)
SMI06 Connection(06800020): Process request Message: (07560470) serviceId(0), se
quenceNumber(30492). SUCCEEDED (00000000)
DPB AddRef DPB_MARSHALING(06801488) refCount(1)
DPB AddRef DPB_MARSHALING(06801488) refCount(2)
DPB Release DPB_MARSHALING(06801488) refCount(1)
SMI01 Connection(06800020): Create Message: (068006A0), initial size 0 bytes
Write Release Request: 30381
DPB45 SessionId (00FDDAF8): Release Object: instanceId(000076AD)
SMI03 Connection(06800020): Send Message: (068006A0) sequenceNumber(146) Asynchr
onous. ... (00000000)
WSD08 Send: result = 0
SMI03 Connection(06800020): Send Message: (068006A0) sequenceNumber(146) Asynchr
onous. SUCCEEDED (00000000)
DPB Release DPB_MARSHALING(06801488) refCount(0)
SMI Release SMI_TRACE(00FDE608) refCount(6)
DPB Release DPB_MARSHALING(06800958) refCount(1)
DPB Release DPB_MARSHALING(06800958) refCount(0)
SMI Release SMI_TRACE(00FDE608) refCount(5)
DPB55 Memory Session : (068001A0) count(1075), total(352256), alloc(212421)
, free(129953)
DPB56 Memory Proc Common : count(17), total(86016), alloc(1294), free(80476)
DPB Release DPB_SESSION_SERVICE(068001A0) refCount(2)
SMI AddRef SMI_TRACE(00FDE608) refCount(6)
DPB AddRef DPB_MARSHALING(06800958) refCount(1)
DPB AddRef DPB_MARSHALING(06800958) refCount(2)
Read Destroy Request: 136
DPB44 SessionId (075615C0): Destroy Object: instanceId(00000088)

SUCCEEDED (00000000)
SMI01 Connection(06800020): Create Message: (068006A0), initial size 0 bytes
SMI03 Connection(06800020): Send Reply Message: (068006A0) sequenceNumber(30492)
Asynchronous. ... (00000000)
WSD08 Send: result = 0
WSD07 ReadHeader: Proto = 24576, Len = 83
SMI01 Connection(06800020): Create Message: (075616B0), initial size 83 bytes
SMI03 Connection(06800020): Send Reply Message: (068006A0) sequenceNumber(30492)
Asynchronous. SUCCEEDED (00000000)
DPB AddRef DPB_SESSION_SERVICE(068001A0) refCount(3)
DPB49 SessionId (075615C0): Send Result : SUCCEEDED (00000000)
DPB40 SessionId (075615C0): Handle Request: DISCONNECT(2), streamVer(0). SUCCEED
ED (00000000)
DPB Release DPB_MARSHALING(06800958) refCount(1)
DPB AddRef DPB_SESSION_SERVICE(068001A0) refCount(4)
DPB Release DPB_MARSHALING(06800958) refCount(0)
DPB Release DPB_SESSION_SERVICE(068001A0) refCount(3)
SMI Release SMI_TRACE(00FDE608) refCount(5)
SMI06 Connection(06800020): Process request Message: (075616B0) serviceId(0), se
quenceNumber(30495). SUCCEEDED (00042137)
DPB55 Memory Session : (068001A0) count(1064), total(352256), alloc(212064)
, free(130309)
DPB56 Memory Proc Common : count(14), total(86016), alloc(1097), free(80673)
DPB Release DPB_SESSION_SERVICE(068001A0) refCount(2)
DPB21 Connection(068001A0): ClientDisconnect: userId(asiadc), connectString(), s
essionId(075615C0). ... (00000000)
DPB21 Connection(068001A0): ClientDisconnect: userId(asiadc), connectString(), s
essionId(075615C0). SUCCEEDED (00000000)
SMI01 Connection(06800020): Create Message: (068006A0), initial size 0 bytes
SMI03 Connection(06800020): Send Reply Message: (068006A0) sequenceNumber(30495)
Asynchronous. ... (00000000)
WSD08 Send: result = 0
SMI03 Connection(06800020): Send Reply Message: (068006A0) sequenceNumber(30495)
Asynchronous. SUCCEEDED (00000000)
SMI08 Connection(06800020): Disconnect: ... (00000000)
WSD09 SendDisconnect: result = 0
WSD06 ReadHeader: Received disconnect code = FF
WSD04 Release: RefCount for connection object = 2
WSD04 Release: RefCount for connection object = 2
SMI Release SMI_CONNECTION(06800020) refCount(2)
SMI08 Connection(06800020): Disconnect: SUCCEEDED (00000000)
SMI Release SMI_TRACE(00FDE608) refCount(4)
DPB Release DPB_SESSION_SERVICE(068001A0) refCount(1)
SMI Release SMI_CONNECTION(06800020) refCount(1)
DPB56 Memory Proc Common : count(11), total(86016), alloc(733), free(81039)
DPB Release DPB_SESSION_SERVICE(068001A0) refCount(0)
DPB Release DPB_Connection(07561730) refCount(0)
SMI Release SMI_CONNECTION(06800020) refCount(0)
SMI Release SMI_TRACE(00FDE608) refCount(3)
SMI Release SMI_LISTENER(00FDE760) refCount(1)
SMI Release SMI_TRACE(00FDE608) refCount(2)

This is from the schedule.log on the Master PC
for ththe trace period:
9/3/2004 09:33:42 0 16 0 New Order Create BG Job Semaphore file(s) P:\ORDCREAT.TAG found. Submitting job to the queue.
9/3/2004 09:33:42 0 4 0 Material Transfer Agent BackGround #2 contacted.
9/3/2004 09:33:42 0 4 0 Material Transfer Remote job posted for execution.
9/3/2004 09:33:42 0 16 0 New Order Create BG Job Job started.
9/3/2004 09:33:43 0 16 0 New Order Create BG Job Agent BackGround #2 contacted.
9/3/2004 09:33:43 0 16 0 New Order Create BG Job Remote job posted for execution.
9/3/2004 09:33:54 0 4 0 Material Transfer Connection to BackGround #2 closed.
9/3/2004 09:33:54 0 4 0 Material Transfer Job finished.
9/3/2004 09:33:55 0 16 0 New Order Create BG Job Connection to BackGround #2 closed.
9/3/2004 09:37:23 0 16 0 New Order Create BG Job Job finished.

Hope this helps.
Norm

I was actually asking for the trace from Master. I wanted to see how it communicates to the agent and what it does after the disconnect.

: Had Trace option set on Master and not Remote. The
: following is the trace from the remote PC: SMI AddRef SMI_TRACE(00FDE608)
: refCount(7)
: DPB AddRef DPB_MARSHALING(06801488) refCount(1)
: DPB AddRef DPB_MARSHALING(06801488) refCount(2)
: DPB Release DPB_MARSHALING(06801488) refCount(1)
: SMI01 Connection(06800020): Create Message: (068006A0), initial size 0 bytes
: Write Invoke Request: 30381.uf_remoteexitcode(QLSISBS)

: Write LONG: value(16)

: Write STRING: value(New Order Create BG Job)

: Write INT: value(1)

: Write STRING: value(Y)

: Write BOOL: value(TRUE)

: Write STRING: value()
: DPB48 SessionId (00FDDAF8): Invoke : instanceId(000076AD), uf_remoteexitc
: ode(QLSISBS), numArgs(6) ASYNCHRONOUS
: SMI03 Connection(06800020): Send Message: (068006A0) sequenceNumber(144)
: Asynchr
: onous. ... (00000000)
: WSD08 Send: result = 0
: WSD07 ReadHeader: Proto = 24576, Len = 87
: SMI01 Connection(06800020): Create Message: (07560470), initial size 87 bytes
: SMI03 Connection(06800020): Send Message: (068006A0) sequenceNumber(144)
: Asynchr
: onous. SUCCEEDED (00000000)
: DPB AddRef DPB_SESSION_SERVICE(068001A0) refCount(3)
: DPB Release DPB_MARSHALING(06801488) refCount(0)
: DPB40 SessionId (075615C0): Handle Request: DELETE_INSTANCE(4), streamVer(0).
: SU
: CCEEDED (00000000)
: SMI Release SMI_TRACE(00FDE608) refCount(6)
: DPB AddRef DPB_SESSION_SERVICE(068001A0) refCount(4)

: SUCCEEDED (00000000)
: DPB Release DPB_SESSION_SERVICE(068001A0) refCount(3)
: SMI AddRef SMI_TRACE(00FDE608) refCount(7)
: SMI06 Connection(06800020): Process request Message: (07560470) serviceId(0),
: se
: quenceNumber(30492). SUCCEEDED (00000000)
: DPB AddRef DPB_MARSHALING(06801488) refCount(1)
: DPB AddRef DPB_MARSHALING(06801488) refCount(2)
: DPB Release DPB_MARSHALING(06801488) refCount(1)
: SMI01 Connection(06800020): Create Message: (068006A0), initial size 0 bytes
: Write Release Request: 30381
: DPB45 SessionId (00FDDAF8): Release Object: instanceId(000076AD)
: SMI03 Connection(06800020): Send Message: (068006A0) sequenceNumber(146)
: Asynchr
: onous. ... (00000000)
: WSD08 Send: result = 0
: SMI03 Connection(06800020): Send Message: (068006A0) sequenceNumber(146)
: Asynchr
: onous. SUCCEEDED (00000000)
: DPB Release DPB_MARSHALING(06801488) refCount(0)
: SMI Release SMI_TRACE(00FDE608) refCount(6)
: DPB Release DPB_MARSHALING(06800958) refCount(1)
: DPB Release DPB_MARSHALING(06800958) refCount(0)
: SMI Release SMI_TRACE(00FDE608) refCount(5)
: DPB55 Memory Session : (068001A0) count(1075), total(352256), alloc(212421)
: , free(129953)
: DPB56 Memory Proc Common : count(17), total(86016), alloc(1294), free(80476)
: DPB Release DPB_SESSION_SERVICE(068001A0) refCount(2)
: SMI AddRef SMI_TRACE(00FDE608) refCount(6)
: DPB AddRef DPB_MARSHALING(06800958) refCount(1)
: DPB AddRef DPB_MARSHALING(06800958) refCount(2)
: Read Destroy Request: 136
: DPB44 SessionId (075615C0): Destroy Object: instanceId(00000088)

: SUCCEEDED (00000000)
: SMI01 Connection(06800020): Create Message: (068006A0), initial size 0 bytes
: SMI03 Connection(06800020): Send Reply Message: (068006A0)
: sequenceNumber(30492)
: Asynchronous. ... (00000000)
: WSD08 Send: result = 0
: WSD07 ReadHeader: Proto = 24576, Len = 83
: SMI01 Connection(06800020): Create Message: (075616B0), initial size 83 bytes
: SMI03 Connection(06800020): Send Reply Message: (068006A0)
: sequenceNumber(30492)
: Asynchronous. SUCCEEDED (00000000)
: DPB AddRef DPB_SESSION_SERVICE(068001A0) refCount(3)
: DPB49 SessionId (075615C0): Send Result : SUCCEEDED (00000000)
: DPB40 SessionId (075615C0): Handle Request: DISCONNECT(2), streamVer(0).
: SUCCEED
: ED (00000000)
: DPB Release DPB_MARSHALING(06800958) refCount(1)
: DPB AddRef DPB_SESSION_SERVICE(068001A0) refCount(4)
: DPB Release DPB_MARSHALING(06800958) refCount(0)
: DPB Release DPB_SESSION_SERVICE(068001A0) refCount(3)
: SMI Release SMI_TRACE(00FDE608) refCount(5)
: SMI06 Connection(06800020): Process request Message: (075616B0) serviceId(0),
: se
: quenceNumber(30495). SUCCEEDED (00042137)
: DPB55 Memory Session : (068001A0) count(1064), total(352256), alloc(212064)
: , free(130309)
: DPB56 Memory Proc Common : count(14), total(86016), alloc(1097), free(80673)
: DPB Release DPB_SESSION_SERVICE(068001A0) refCount(2)
: DPB21 Connection(068001A0): ClientDisconnect: userId(asiadc),
: connectString(), s
: essionId(075615C0). ... (00000000)
: DPB21 Connection(068001A0): ClientDisconnect: userId(asiadc),
: connectString(), s
: essionId(075615C0). SUCCEEDED (00000000)
: SMI01 Connection(06800020): Create Message: (068006A0), initial size 0 bytes
: SMI03 Connection(06800020): Send Reply Message: (068006A0)
: sequenceNumber(30495)
: Asynchronous. ... (00000000)
: WSD08 Send: result = 0
: SMI03 Connection(06800020): Send Reply Message: (068006A0)
: sequenceNumber(30495)
: Asynchronous. SUCCEEDED (00000000)
: SMI08 Connection(06800020): Disconnect: ... (00000000)
: WSD09 SendDisconnect: result = 0
: WSD06 ReadHeader: Received disconnect code = FF
: WSD04 Release: RefCount for connection object = 2
: WSD04 Release: RefCount for connection object = 2
: SMI Release SMI_CONNECTION(06800020) refCount(2)
: SMI08 Connection(06800020): Disconnect: SUCCEEDED (00000000)
: SMI Release SMI_TRACE(00FDE608) refCount(4)
: DPB Release DPB_SESSION_SERVICE(068001A0) refCount(1)
: SMI Release SMI_CONNECTION(06800020) refCount(1)
: DPB56 Memory Proc Common : count(11), total(86016), alloc(733), free(81039)
: DPB Release DPB_SESSION_SERVICE(068001A0) refCount(0)
: DPB Release DPB_Connection(07561730) refCount(0)
: SMI Release SMI_CONNECTION(06800020) refCount(0)
: SMI Release SMI_TRACE(00FDE608) refCount(3)
: SMI Release SMI_LISTENER(00FDE760) refCount(1)
: SMI Release SMI_TRACE(00FDE608) refCount(2)

: This is from the schedule.log on the Master PC
: for ththe trace period: 9/3/2004 09:33:42 0 16 0 New Order Create BG Job
: Semaphore file(s) P:\ORDCREAT.TAG found. Submitting job to the queue.
: 9/3/2004 09:33:42 0 4 0 Material Transfer Agent BackGround #2 contacted.
: 9/3/2004 09:33:42 0 4 0 Material Transfer Remote job posted for execution.
: 9/3/2004 09:33:42 0 16 0 New Order Create BG Job Job started.
: 9/3/2004 09:33:43 0 16 0 New Order Create BG Job Agent BackGround #2
: contacted.
: 9/3/2004 09:33:43 0 16 0 New Order Create BG Job Remote job posted for
: execution.
: 9/3/2004 09:33:54 0 4 0 Material Transfer Connection to BackGround #2 closed.
: 9/3/2004 09:33:54 0 4 0 Material Transfer Job finished.
: 9/3/2004 09:33:55 0 16 0 New Order Create BG Job Connection to BackGround #2
: closed.
: 9/3/2004 09:37:23 0 16 0 New Order Create BG Job Job finished.

: Hope this helps.
: Norm

: I was actually asking for the trace from Master. I wanted to see how it
: communicates to the agent and what it does after the disconnect.
I had the trace turn on on both the Master and the
remote PC but the only one that showed a trace was
remote PC.
Norm

You don't have it turned on in the Remote Agent profile setting on the Master that's why you don't see it.

: I had the trace turn on on both the Master and the
: remote PC but the only one that showed a trace was
: remote PC.
: Norm

OK I may have it is time. Also I went back to
version 3.4.4 and the problem went away. I updated
to version 3.4.21 and the problem came back. the
following is the trace from the master PC:

DPB01 Connection(066416A0): ConnectToServer : application(1097), location(ROCBK0
0AD02000), driver(WinSock). ... (00000000)
DPB01 Connection(066416A0): ConnectToServer : application(1097), location(ROCBK0
0AD02000), driver(WinSock). SUCCEEDED (00000000)
DPB43 SessionId (07C60128): Create Object : className(n_gateway), instanceId(FFF
FFFFF). ... (00000000)
DPB43 SessionId (07C60128): Create Object : className(n_gateway), instanceId(000
00468). SUCCEEDED (00000000)
DPB48 SessionId (07C60128): Invoke : instanceId(00000468), uf_executejob(
QCn_gateway.O), numArgs(2) ASYNCHRONOUS
DPB48 SessionId (00FDDB38): Invoke : instanceId(00000177), uf_remoteexitc
ode(QLSISBS), numArgs(6) ASYNCHRONOUS

SUCCEEDED (00000000)
DPB45 SessionId (00FDDB38): Release Object: instanceId(00000177)
DPB44 SessionId (07C60128): Destroy Object: instanceId(00000468)
DPB02 Connection(066416A0): DisconnectServer: ... (00000000)
DPB02 Connection(066416A0): DisconnectServer: SUCCEEDED (00000000)

Schedule.Log File:
9/3/2004 15:29:59:827 0 16 New Order Create BG Job Job started.
9/3/2004 15:29:59:997 0 16 New Order Create BG Job Agent BackGround #2 contacted.
9/3/2004 15:30:00:088 0 16 New Order Create BG Job Remote job posted for execution.
9/3/2004 15:30:14:208 0 16 New Order Create BG Job Connection to BackGround #2 closed.
9/3/2004 15:33:43:929 0 16 New Order Create BG Job Job finished.
9/3/2004 15:36:00:746 0 19 New Order from As/400 Job started.

At this point I am temporally going back to v3.4.4,
in that I will be out for the next week.
Norm

Ok, I probably know now what is causing this problem. In the Remote Agent Profile properties uncheck the Asynchronus option. This option cause the Master to poll for events and this leads to high CPU usage.

: OK I may have it is time. Also I went back to
: version 3.4.4 and the problem went away. I updated
: to version 3.4.21 and the problem came back. the
: following is the trace from the master PC: DPB01 Connection(066416A0):
: ConnectToServer : application(1097), location(ROCBK0
: 0AD02000), driver(WinSock). ... (00000000)
: DPB01 Connection(066416A0): ConnectToServer : application(1097),
: location(ROCBK0
: 0AD02000), driver(WinSock). SUCCEEDED (00000000)
: DPB43 SessionId (07C60128): Create Object : className(n_gateway),
: instanceId(FFF
: FFFFF). ... (00000000)
: DPB43 SessionId (07C60128): Create Object : className(n_gateway),
: instanceId(000
: 00468). SUCCEEDED (00000000)
: DPB48 SessionId (07C60128): Invoke : instanceId(00000468), uf_executejob(
: QCn_gateway.O), numArgs(2) ASYNCHRONOUS
: DPB48 SessionId (00FDDB38): Invoke : instanceId(00000177), uf_remoteexitc
: ode(QLSISBS), numArgs(6) ASYNCHRONOUS

: SUCCEEDED (00000000)
: DPB45 SessionId (00FDDB38): Release Object: instanceId(00000177)
: DPB44 SessionId (07C60128): Destroy Object: instanceId(00000468)
: DPB02 Connection(066416A0): DisconnectServer: ... (00000000)
: DPB02 Connection(066416A0): DisconnectServer: SUCCEEDED (00000000)

: Schedule.Log File: 9/3/2004 15:29:59:827 0 16 New Order Create BG Job Job
: started.
: 9/3/2004 15:29:59:997 0 16 New Order Create BG Job Agent BackGround #2
: contacted.
: 9/3/2004 15:30:00:088 0 16 New Order Create BG Job Remote job posted for
: execution.
: 9/3/2004 15:30:14:208 0 16 New Order Create BG Job Connection to BackGround
: #2 closed.
: 9/3/2004 15:33:43:929 0 16 New Order Create BG Job Job finished.
: 9/3/2004 15:36:00:746 0 19 New Order from As/400 Job started.

: At this point I am temporally going back to v3.4.4,
: in that I will be out for the next week.
: Norm

: Ok, I probably know now what is causing this problem. In the Remote Agent
: Profile properties uncheck the Asynchronus option. This option cause the
: Master to poll for events and this leads to high CPU usage.
The Asynchronus Operation, in the Remote Host Profile
setup on the master PC, is NOT Checked.
Norm

How about the job run mode is it synchronous or asynchronous.

Do you have the same 24x7 version or different versions installed on the master and the remote?
The reason I am asking this because there were some changes made in the internal communication protocol. In the recent version 24x7 master expects to receive complete remote job ending info including error messages (if any) and not just the status code (success or failure). If you run different versions this could also leads to the mentioned problem.

: Ok, I probably know now what is causing this problem. In the Remote Agent
: Profile properties uncheck the Asynchronus option. This option cause the
: Master to poll for events and this leads to high CPU usage.

What about the version question?

: The Asynchronus Operation, in the Remote Host Profile
: setup on the master PC, is NOT Checked.
: Norm