Ansicht
Dokumentation
01792 - Delete a client procedure - missing environment variable ?
CPI1466 during Backup CPI1466 during BackupThis documentation is copyright by SAP AG.
Delete a client procedure - missing environment variable ?
I think you (and Wilbert) are correct about the full path (especiallyconsidering I am crossing boxes) and next time I have a client delete, I
will try this. As to Betsy's question. We are at 40B, kernel 749. The last
delete through SCC5 was 14.2Gig (from DB02) and took 6 hours: 20 minutes.
The R3trans delete client was 15.2 Gig (also from DB02) and took 3 hours: 45
minutes (basically half as long). The short answer to why we have two
clients in PRD is the old "We took a vote and you lost". The second client
was created in order to bring two new companies up to speed with the other
production companies (and copy oodles of material masters, BOM's, etc.) In
addition, one of the companies had serious W2 issues at the end of 1999 and
used the "pre-production" client to re-run their payroll for the entire
year! This data is still very dear to them. As of this note, I am
considering compressing the disks - talk to me babe.
Rick
-----Original Message-----
From: Mike Martin, IS, Sousa [mailto:MMartinZs...]
Sent: Thursday, April 19, 2001 6:39 PM
To: Rick Githens
Cc: sap400Zm...
Subject: RE: Delete a client procedure - missing environment variable ?
Rick,
Wilbert is right on deleting in batch, the full path name is needed. Also,
have you considered compressing your dev server disks? This may allow you a
full copy of PRD. Lastly, why do you have two clients on PRD? Is one a
training client, test client, etc? Perhaps more suggestions to follow,
depending on your answers...
Regards,
Mike D. Martin
SAP Basis Administrator
SOLA Optical, USA
707-763-9911 x6106
mmartinZs...
-----Original Message-----
From: Karremans WLA [ mailto:wkaZo... <mailto:wkaZo...> ]
Sent: Thursday, April 19, 2001 2:50 PM
To: 'Betsy Strebe'; Rick Githens
Cc: sap400Zm...
Subject: RE: Delete a client procedure - missing environment variable ?
Hello everyone;
I did this week a successful delete of a client in the batch (sbmjob).
The log file was NOT present before I started the job.
I needed to specify the fully qualified path, because the cd /usr/sap/trans
was not transferred to the batch job (why not ?). I used the CPYENVVAR(*YES)
(don't know why).
SBMJOB CMD(R3trans '-w usr/sap/trans/log/dltclnt.log -u 1
usr/sap/trans/bin/dltclnt.ctl')
CPYENVVAR(*YES)
Wilbert
-----Original Message-----
From: Betsy Strebe [ mailto:bstrebeZt...
<mailto:bstrebeZt...> ]
Sent: donderdag 19 april 2001 22:58
To: Rick Githens
Cc: sap400Zm...
Subject: Re: Delete a client procedure - missing environment variable ?
Rick,
I could never get it to submit to batch either. I have no recollection of
the exact error, but the type you are getting sounds very familiar. After
exhausting my knowlege on job environments and background jobs, in
desparation I went back to a remote client copy that weekend. Both Claudia
and Mike Martin were helpful in offering the OS delete procedures. Maybe
they can be more explicit on how to get this to work in the background.
Also, Rick, could you give us stats on the interactive OS delete? DB size,
system config, R/3 release, kernel, time?
thanks,
Betsy
~~~~~~~~~~~~~~~~~~~~~~
Betsy Strebe
bstrebeZt...
Systems Technical Manager
Trinchero Family Estates
Sutter Home Wines, Inc.
(707) 963-3104 ext. 2439
www.tfewines.com
~~~~~~~~~~~~~~~~~~~~~~~
Rick Githens
<RGithensZgiorgio To: "'SAP400 ListServer'"
<sap400Zm...>
foods.com> cc:
Subject: Delete a client
procedure - missing environment variable ?
04/19/01 12:45 PM
The extract that follows is from a pre-consolut post about deleting clients at
the os level and it works like a champ interactively (green screen)(thank
you very much Claudia and Betsy). However, when I follow the instructions
to
submit the job, it always bombs trying to read the control file. I used the
cpyenvvar(*yes) for the submit but when I wrkenvvar, the only environmant
variable that shows up is 'WRKLNKSAP' with a value of ' ' no matter what my
current directory is. Should I set some other environment variable(s)
before
doing the submit job?
Thanks,
Rick Githens
delete a client procedure:
----- Original Message -----
From: "Betsy Strebe"
To: <sap400Zm...>
Sent: Friday, October 13, 2000 5:37 PM
Subject: delete a client procedure
A client copy request just came through my doors - isn't it Friday???
Anyway, I am planning to delete the client (320 in TST) first this weekend,
and I know there was some discussion here earlier about performing this
from
the OS level with R3trans. Of course, I can't find any of those posts.
But
in looking in Hernandez, I think this is what I should do.
1) Create a control file in /usr/sap/trans/bin with any name - say
DELTST320:
Clientremove
Client=320
Select *
2) From the OS as TSTOFR, execute the command:
R3trans -w deltst320.log -u 1 deltst320.ctl
My questions are:
a) does this look right?
b) I assume I need the R3trans parameters surrounded by single quotes
(the
book does not have them since it's more for those other machines)?
c) can I submit the R3trans command to batch (so I can do this from
home
and not tie up my computer phone line)?
d) there was no mention of creating the log file (deltst320.log) first,
will this create automatically?
who wanted the weekend off anyway--
thanks in advance,
Betsy
-----Original Message-----
From: Claudia Pillich
Sent: Friday, October 13, 2000 3:14 PM
To: Betsy Strebe; sap400Zm...
Subject: Re: delete a client procedure
a) Do a cd /usr/sap/trans before the command, then your command looks as
follows:
R3trans '-w log/deltst320.log -u 1 bin/deltst320.ctl'
b) Yes, you need the single quotes.
c) Yes, you can submit it to batch. I would write a quickie CL program to
do the cd and the R3trans, or you can do the cd first then on your SBMJOB
command use CPYENVVAR(*YES).
d) Yes, it automatically creates the log file.
Durban Tours - Südafrika Safari
General Material Data General Material Data
This documentation is copyright by SAP AG.
Length: 8456 Date: 20240520 Time: 230449 sap01-206 ( 3 ms )
